mirror of
https://github.com/tamasfe/taplo.git
synced 2025-12-23 12:26:50 +00:00
A TOML toolkit written in Rust
d4d1fcb668
Some checks failed
Continuous integration / Check formatting (push) Has been cancelled
Continuous integration / Test on Rust stable (push) Has been cancelled
Continuous integration / Check on WASM (push) Has been cancelled
Continuous integration / Run toml-test (push) Has been cancelled
Continuous integration / Test libraries with MSRV (push) Has been cancelled
Continuous integration / Test binaries with MSRV (push) Has been cancelled
Continuous integration / Test WASM with MSRV (push) Has been cancelled
Continuous integration / Tag Releases (push) Has been cancelled
According to the toml standard, bare keys may only contain the characters A-Za-z0-9_- and they must contain at least one character. This allows identifiers to look like dates, e.g. 2024-01-01. Due to a bug in the lexing library logos, some-like identifiers are incorrectly being parsed as INTEGER tokens, while date-like identifiers in table names are being parsed as DATE tokens as they should be. Due to this bug, date-like identifiers were being accepted in some situations by taplo while they were rejected in other situations. This commit only allows DATE tokens in identifiers (as they should be, according to the standard). It does not fix the underlying bug that sometimes produces incorrect INTEGER tokens instead of DATE tokens. |
||
|---|---|---|
| .github | ||
| .vscode | ||
| crates | ||
| docker | ||
| editors/vscode | ||
| js | ||
| scripts | ||
| site | ||
| test-data | ||
| util/test-gen | ||
| .dockerignore | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| docker-bake.hcl | ||
| LICENSE | ||
| pyproject.toml | ||
| README.md | ||
| rustfmt.toml | ||
| taplo-icon.png | ||
| taplo-icon.svg | ||
| taplo.toml | ||
Taplo
This is the repository for Taplo, a TOML v1.0.0 toolkit, more details on the website.
Status
The project is very young, so bugs and incomplete features are expected, so any help is welcome!
The correctness of the TOML parsing and decoding is not yet entirely guaranteed (as there is no official 1.0.0 compliance test suite yet).
Contributing
All kinds of contributions are welcome. Make sure to read the CONTRIBUTING.md first!