search

cloudmesh / cloudmesh-flow

Workflow for cloudmesh
Other
1 stars 1 forks source link

future work: parsing issues #24

Open robludwig opened 5 years ago

robludwig commented 5 years ago

We use lark for parsing, and we have a grammar defined for workflow strings in the WorkFlow file. However it is missing support for numerical and non-letter values, and has a subtle bug with long (potentially ambiguous?) strings like node1 ; node2 || node3; node4 || node5. What should this parse to? Lark actually has support for indicating when something has an ambiguous parsing.

Currently we resolve this by using parentheses, which work correctly.

robludwig commented 5 years ago

Also, when there is an error parsing the parser emits a long error. Perhaps we should catch that and re-throw a new, better exception