You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The point is to make dynamic literals, set externally by a configuration file or internally during the parse. The examples given are real, taken from a current project.
The text was updated successfully, but these errors were encountered:
If you want to swap out predefined strings, consider using resource strings. This was designed to support language translation for Gherkin specifically.
wildcard + assertion (. &{ ... })*
Very powerful approach for regular strings or PEG-parseable strings.
#PARSE expressions
Full control over the cursor and parse result. Shell out to some other parser and use the length of what is returned.
I am still not closing this issue because I think your suggestion is worth considering as an extension.
So we have code assertions to control parsing, and code expressions to define a return value.
I propose code Literals, which represent C# code that returns a literal value, as a string, to be used by the parser.
becomes
The point is to make dynamic literals, set externally by a configuration file or internally during the parse. The examples given are real, taken from a current project.
The text was updated successfully, but these errors were encountered: