-
Notifications
You must be signed in to change notification settings - Fork 3
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
Backslash/semicolon/octothorpe escaping #5
Comments
yes |
I stay neutral on this for two reasons:
I'd enjoy to see if this could lead to a discussion how a ini-file is formally defined and how people may safely add custom properties. |
yes |
no Because I rather see it done properly by defining a formal grammar instead of just a quick fix. |
On one hand I think the vote is to early, on the other hand it might be the spark to start the discussion about a formally defined file format. I personally I tend to vote "No" as I think that the file format should be as simple as possible. Anyway, I agree with @sindresorhus and @florianb: We need a strong formal specification and I'm willing to contribute. PS: I'm not implementing something new, I just implemented a Vim editorconfig plugin. While implementing I missed a formal specification. |
no, I too would like a more in depth spec including learning what INI does here. |
The conclusion is no. Closed |
In property values (outside globs inside brackets), should we add backslash/semicolon/octothorpe escaping into EditorConfig specification? Please vote by commenting below: yes or no only. Voting will be closed at the end of May 6.
Related/discussion issue editorconfig/editorconfig-core-test#24
@editorconfig/board-member cc @rakus
The text was updated successfully, but these errors were encountered: