-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify parsing ambiguity of "parameters" in Link Object #3276
Comments
There's a further ambiguity: the property names under In this case, there's an easy solution which is that if you (for some bizarre reason) have a parameter named |
PRs merged – closing! |
The question came up in today's call about fields that could take either a literal value or a runtime expression. The
parameters
field in the Link Object allows this. Probably we should clarify that anything that parses as a runtime expression SHOULD (MUST?) be handled that way, and that it's therefore not possible to specify a literal value that looks like a runtime expression (since creating an escaping syntax would require a minor version increment).cc @webron @mkistler
The text was updated successfully, but these errors were encountered: