Skip to content
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

Jump to bottom

Keys should be identifier-like (addresses #65) #67

Closed
wants to merge 1 commit into from
Closed

Keys should be identifier-like (addresses #65) #67

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
11 changes: 6 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,6 +149,9 @@ Hash me

There are two ways to make keys. I call them "key groups" and "keys". Both are
just regular keys, but key groups only ever have a single hash as their value.
Keys contain only letters, numbers or underscore (`_`) characters, and must
start with a letter or underscore. Name your key groups whatever crap you
please, just don't use funny characters. They cause trouble. OBEY.

Key groups appear in square brackets on a line by themselves. You can tell them
apart from arrays because arrays are only ever values.
Expand All @@ -158,9 +161,8 @@ apart from arrays because arrays are only ever values.
```

Under that, and until the next key or EOF are the key/values of that key group.
keys are on the left of the equals sign and values are on the right. Keys start
with the first non-whitespace character and end with the last non-whitespace
character before the equals sign.
Keys are on the left of the equals sign and values are on the right. You can put
whitespace in between, but that's all you get: key, equals sign, value. Simple.

```toml
[keygroup]
Expand All @@ -170,8 +172,7 @@ key = "value"
You can indent keys and their values as much as you like. Tabs or spaces. Knock
yourself out. Why, you ask? Because you can have nested hashes. Snap.

Nested hashes are denoted by key groups with dots in them. Name your key groups
whatever crap you please, just don't use a dot. Dot is reserved. OBEY.
Nested hashes are denoted by key groups with dots in them.

```toml
[key.tater]
Expand Down