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
According to the 'conf_parse.peg' a comment is specified as any line that begins with a '#' sign (leading whitespace is allowed). However a '#' character appearing within a value (no leading whitespace) is treated as a comment as well. Is this intentional?
Yes, that is intentional, so that trailing comments are allowed. We could potentially tweak the grammar such that you could quote the RHS or escape the #.
I also need the support for # in the config value.
escpaping \# or "quo#ting" are both okay with me. within quoting then again with support for escpaing of " like "quo#\"ting".
According to the 'conf_parse.peg' a comment is specified as any line that begins with a '#' sign (leading whitespace is allowed). However a '#' character appearing within a value (no leading whitespace) is treated as a comment as well. Is this intentional?
PS: my use case is the configuration of a MQTT topic pattern which uses '#' as a wildcard character.
The text was updated successfully, but these errors were encountered: