OPG-496: Update docs with template variable syntax #1045
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Template variable interpolation syntax rules have changed somewhat in OPG v9. To reduce ambiguity in parsing, you can only use
$variable
syntax if the variable is surrounded by whitespace, or at least ends in whitespace.If the variable is part of a contiguous "word", users need to use the
${variable}
syntax. Therefore some constructs that were valid in OPG v8 and before are no longer valid in v9.Examples - if there is a template variable
node
:Valid:
$node
Valid (but not preferred):
index_$node
Valid (preferred):
index_${node}
Invalid:
$node_index
(this will be an error since OPG interprets this as the template variablenode_index
)Valid:
${node}_index
This PR just updates some documentation to explain this syntax.
External References