-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
KDL 2.0: identifier-based quoteless strings #339
Labels
Comments
zkat
added
enhancement
New feature or request
breaking
This can only be done for the next major version of KDL
labels
Nov 28, 2023
I think this, especially when combined with #340, can be very confusing. Of course a good linter can prevent such confusion. E.g.
Or
|
After thinking about it I think I'm going to withdraw this. I have an alternative proposal. |
This was referenced Dec 10, 2023
After conversation in #350, it looks like this is what we're gonna go with after all... |
zkat
added a commit
that referenced
this issue
Dec 13, 2023
zkat
added a commit
that referenced
this issue
Dec 13, 2023
This has been merged into the kdl-v2 branch |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I thought a lot about this (and we've talked about this at length in #308, but I think we should just do it, and that it's going to be ok. In practice, there will be ways to catch typos in a reasonable way, and I think quoteless strings (following identifier syntax) are actually a huge UX improvement for human-authored/maintained configuration files.
Feel free to protest this change here, or up/downvote with reactji, but I'm now leaning towards this being a major KDL 2.0 change.
The text was updated successfully, but these errors were encountered: