Description
Currently parser commands that accept string options handle multiple token types separately.
Example:
- Single quoted
'value'
- Double quoted
"value"
- Plain
value
This forces consumer to check for quotes and normalize the the value manually. A cleaner solution would be to introduce a NORMAL_STRING token for all string option values, which would return a plain value and use that across all commands.
Motivation
- Simplifies parser rules and downstream processing
- Ensures consistent string handling across commands
- Reduces potential bugs caused by inconsistent quoting
Description
Currently parser commands that accept string options handle multiple token types separately.
Example:
'value'"value"valueThis forces consumer to check for quotes and normalize the the value manually. A cleaner solution would be to introduce a
NORMAL_STRINGtoken for all string option values, which would return a plain value and use that across all commands.Motivation