-
Notifications
You must be signed in to change notification settings - Fork 856
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
Clarify line-ending backslash in multi-line strings #728
Comments
That's a good proposal. Could you open a PR with that change, mentioning #728 in your description? |
Regarding testing, you could ask in #585. |
If it would fit, I'd say yes. I wasn't even thinking about that, but good call.
You were asking about the state of testing. I wanted to keep that separate, which is why I referred you to #585. |
Great, that's what I thought you meant but just wanted to clarify. I've just pushed the wording change and made #729. I noticed that |
Your PR looks good to me. Hoping it gets merged soon. @pradyunsg @mojombo Can we merge #729? |
I'm not even sure about test commits, to be honest. Again, read #585 and bring up this particular issue, and ask where tests should go. |
Got it. Thanks! |
Gonna go ahead and close this. Let's keep the testing question separate. |
The v1.0.0-rc.1 spec says, regarding multi-line strings:
This is unclear for the case when that last
\
is escaped. I think the ABNF is correct and when I tested with tomlkit it looks good:But I think the description in the spec can be clearer. I propose the following 1-word change (or 2 if you include the epenthesis of the preceding "a" to "an"):
The code snippet above might also be a good test case.
Aside: Is https://github.com/BurntSushi/toml-test the de jure, or even de facto, test set? It hasn't been updated in a while.
The text was updated successfully, but these errors were encountered: