-
Notifications
You must be signed in to change notification settings - Fork 26
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
Nested table keys not supported #51
Comments
Dotted keys don't seem to work either. Dotted keys example from toml spec... name = "Orange"
physical.color = "orange"
physical.shape = "round" Throws the following error... Uncaught [SyntaxError: Expected "=", [ \t] or [A-Za-z0-9_\-] but "." found.] {
message: 'Expected "=", [ \\t] or [A-Za-z0-9_\\-] but "." found.',
expected: [
{ type: 'literal', value: '=', description: '"="' },
{ type: 'class', value: '[ \\t]', description: '[ \\t]' },
{
type: 'class',
value: '[A-Za-z0-9_\\-]',
description: '[A-Za-z0-9_\\-]'
}
],
found: '.',
offset: 24,
line: 2,
column: 9,
name: 'SyntaxError'
} Is this package no longer being maintained? |
eifinger
added a commit
to astral-sh/ruff-action
that referenced
this issue
Dec 23, 2024
"toml" does not support all TOML features BinaryMuse/toml-node#51
This was referenced Dec 23, 2024
eifinger
added a commit
to astral-sh/ruff-action
that referenced
this issue
Dec 23, 2024
"toml" does not support all TOML features BinaryMuse/toml-node#51 Fixes: #31
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To use an example from the
TOML
README, specifying a nested table as a key using dot syntax like this fails:This was run via the browser tool
The text was updated successfully, but these errors were encountered: