Skip to content

Commit ef0fdef

Browse files
committed
📝 fix JSON Pointer documentation #3511
1 parent b4d5212 commit ef0fdef

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

docs/mkdocs/docs/features/json_pointer.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,11 +18,11 @@ Consider the following JSON document
1818
}
1919
```
2020

21-
Then every value inside the JSON document can be idientified as follows:
21+
Then every value inside the JSON document can be identified as follows:
2222

2323
| JSON Pointer | JSON value |
2424
|-------------------|----------------------------------------------------------------------------------|
25-
| `/` | `#!json {"array":["A","B","C"],"nested":{"one":1,"two":2,"three":[true,false]}}` |
25+
| `` | `#!json {"array":["A","B","C"],"nested":{"one":1,"two":2,"three":[true,false]}}` |
2626
| `/array` | `#!json ["A","B","C"]` |
2727
| `/array/0` | `#!json A` |
2828
| `/array/1` | `#!json B` |
@@ -34,6 +34,9 @@ Then every value inside the JSON document can be idientified as follows:
3434
| `/nested/three/0` | `#!json true` |
3535
| `/nested/three/1` | `#!json false` |
3636

37+
Note `/` does not identify the root (i.e., the whole document), but an object entry with empty key `""`. See
38+
[RFC 6901](https://tools.ietf.org/html/rfc6901) for more information.
39+
3740
## JSON Pointer creation
3841

3942
JSON Pointers can be created from a string:

0 commit comments

Comments
 (0)