Skip to content

Clarify parsing ambiguity of "parameters" in Link Object #3276

@handrews

Description

@handrews

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

Metadata

Metadata

Assignees

Labels

clarificationrequests to clarify, but not change, part of the speclinks

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions