Skip to content

Clarify the reason empty keys are allowed #1095

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.

Sign up for GitHub

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

Open
arp242 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify the reason empty keys are allowed #1095

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,12 @@

## unreleased

- Clarify that tables typically cannot be nested infinitely [#1087]).
- Clarify that tables typically cannot be nested infinitely ([#1087]).

- Clarify the reason for allowing empty keys ([#1095]).

[#1087]: https://github.com/toml-lang/toml/pull/1087
[#1095]: https://github.com/toml-lang/toml/pull/1095

## 1.1.0 / 2025-12-18

Expand Down
7 changes: 5 additions & 2 deletions toml.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,8 +129,11 @@ to use bare keys except when absolutely necessary.
'quoted "value"' = "value"
```

A bare key must be non-empty, but an empty quoted key is allowed (though
discouraged). You cannot use multi-line strings to define quoted keys.
You cannot use multi-line strings to define quoted keys.

TOML tables correspond to hash tables (also known as dictionaries) which usually
permit any string value. For that reason empty quoted keys are allowed, though
discouraged. A bare key must be non-empty.

```toml
= "no key name" # INVALID
Expand Down