-
Notifications
You must be signed in to change notification settings - Fork 62
Open
Description
Hi,
I'm proposing to introduce a complete grammars for describing syntax of following runtime expression types:
"$steps." name
"$workflows." name
"$sourceDescriptions." name
"$components." name
These types will be replaced by
"$steps." steps-name
"$workflows." workflows-name
"$sourceDescriptions." source-descriptions-name
"$components." components-name
Full grammar for above non-terminals is defined below:
; Secondary grammar for parsing $steps name part
; Format: {stepId}.{field}.{subField}[#/{jsonPointer}]
steps-name = steps-id "." steps-field "." steps-sub-field ["#" json-pointer]
steps-id = 1*(ALPHA / DIGIT / "_" / "-")
steps-field = "outputs"
steps-sub-field = 1*(ALPHA / DIGIT / "." / "-" / "_")
; Secondary grammar for parsing $workflows name part
; Format: {workflowId}.{field}.{subField}[#/{jsonPointer}]
workflows-name = workflows-id "." workflows-field "." workflows-sub-field ["#" json-pointer]
workflows-id = 1*(ALPHA / DIGIT / "_" / "-")
workflows-field = "inputs" / "outputs"
workflows-sub-field = 1*(ALPHA / DIGIT / "." / "-" / "_")
; Secondary grammar for parsing $sourceDescriptions name part
; Format: {sourceName}.{reference}
; reference can be operationId (unconstrained) or workflowId (constrained)
source-descriptions-name = source-descriptions-source-name "." source-descriptions-reference
source-descriptions-source-name = 1*(ALPHA / DIGIT / "_" / "-")
source-descriptions-reference = 1*CHAR
; Secondary grammar for parsing $components name part
; Format: {field}.{subField}
; Allowed fields: inputs, parameters, successActions, failureActions
components-name = components-field "." components-sub-field
components-field = "parameters" / "successActions" / "failureActions"
components-sub-field = 1*(ALPHA / DIGIT / "." / "-" / "_")Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels