-
Notifications
You must be signed in to change notification settings - Fork 743
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
lexer: TOML: Support more integer and floating formats #1832
Conversation
in TOML, the decimal point must be surrounded by at least one digit on each side.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your contribution @ToruNiina ❤️ The PR looks good overall. I have added some suggestions for your consideration. Please let me know what you think 🙏🏼 .
Co-authored-by: Tan Le <[email protected]>
Co-authored-by: Tan Le <[email protected]>
Co-authored-by: Tan Le <[email protected]>
Co-authored-by: Tan Le <[email protected]>
Co-authored-by: Tan Le <[email protected]>
Co-authored-by: Tan Le <[email protected]>
Thank you for your time and effort on the request and many helpful suggestions. I totally agree with the suggestions. I applied all the changes. |
Awesome work @ToruNiina 👍🏼 Let's ship it 🚀 |
Hi,
I wrote this patch to fix #1831 .
I added hex, bin, oct integers and special floating point numbers to the rule. And I modified the existing definition of integer and floating point numbers to allow underscores.
I also added some examples of those new features to
spec/visual/samples/toml
.Then I visually checked that the examples of the features I mentioned in the issue.
In the screenshot I included some invalid examples to check if those are highlighted as an error, but I didn't include them in the
spec/visual/sample
to avoid confusion.If those invalid examples are beneficial, I will add them.
Please check it when you have time.
Thanks!