-
Notifications
You must be signed in to change notification settings - Fork 4
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
TOML local date not supported #5
Comments
Hi @MoritzRitter this should be an issue in the toml parser library we are using. |
The issue arises because the toml package on npm is no longer maintained and only supports TOML specification version 0.4.0, which is outdated. |
Hi @MoritzRitter, You can check it out here: It now successfully parses the toml date values. |
I will check that asap |
Currently, when editing the date, it gets parsed into this format: The smol-toml library includes the time by default when handling dates. Based on their documentation, I couldn’t find a way to adjust the parsing behavior to output this specific date format: Does this work for you? |
Thanks for checking! Let's put it like this: I would need a local date without timezone info etc. And this is not what we have at the moment. But I can work around it. Much better than a parsing error! |
Got it! Since this is related to the smol-toml library, I’ve opened an issue in their repository. Hopefully, they already have this feature or are willing to implement it. |
Hi @MoritzRitter I fixed the issue |
Hi @maliknajjar Thanks for the update. There seems to be a new problem with the preservation of multi-line basic strings (acc. to https://toml.io/en/v1.0.0#string): |
Hi @MoritzRitter, I created a seperate issue for this #7 |
Acc. to https://toml.io/en/v1.0.0#local-date a local date looks like this:
ld1 = 1979-05-27
However, the TOML Viewer & Editor at https://guifier.com/toml reports an error
Error: SyntaxError: Expected "T" but "\n" found.
Expected behavior: the local date is shown and can be edited.
The text was updated successfully, but these errors were encountered: