-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allowing empty values #8
Comments
This PR address #8, introducing our first feature flag to allow for parsing lines that have a key but no value. We also enable running the tests with all features enabled as well as the default. Signed-off-by: Kyle Rader <[email protected]> Co-authored-by: Kyle Rader <[email protected]>
Implemented as proposed in #7. Thank you! |
Reopening because it looks like the spec is likely to explicitly allow empty values in the future. The ideal way forward IMO involves some breaking changes to |
Ah well look at that. Sounds good. The feature flag could be removed then as well when updating it to be the default. |
It turns out that in many config files within a project of ours, empty values are normal and do not cause issues with our IDE's so we'd like our linter to mirror this if possible.
Proposal
Enable empty values to be parsed as empty lines or pairs behind a feature flag so callers can decide what level of enforcement they get.
The text was updated successfully, but these errors were encountered: