mirror of
https://github.com/nushell/nushell.git
synced 2024-11-22 08:23:24 +01:00
e4104d0792
# Description First part of SpanID refactoring series. This PR adds a `SpanId` type and a corresponding `span_id` field to `Expression`. Parser creating expressions will now add them to an array in `StateWorkingSet`, generates a corresponding ID and saves the ID to the Expression. The IDs are not used anywhere yet. For the rough overall plan, see https://github.com/nushell/nushell/issues/12963. # User-Facing Changes Hopefully none. This is only a refactor of Nushell's internals that shouldn't have visible side effects. # Tests + Formatting # After Submitting |
||
---|---|---|
.. | ||
src | ||
Cargo.toml | ||
LICENSE | ||
README.md |
Support for the NUON format.
The NUON format is a superset of JSON designed to fit the feel of Nushell. Some of its extra features are
- trailing commas are allowed
- commas are optional in lists
- quotes are not required around keys or any bare string that do not contain spaces
- comments are allowed, though not preserved when using [
from_nuon
]
Example
below is some data in the JSON format
{
"name": "Some One",
"birth": "1970-01-01",
"stats": [
2544729499973429198,
687051042647753531,
6702443901704799912
]
}
and an equivalent piece of data written in NUON
{
name: "Some One", # the name of the person
birth: "1970-01-01", # their date of birth
stats: [ # some dummy "stats" about them
2544729499973429198,
687051042647753531,
6702443901704799912, # note the trailing comma here...
], # and here
} # wait, are these comments in a JSON-like document?!?!