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

Document restriction on top-level JSON types explicitly #1496

Merged
merged 2 commits into from
May 23, 2023
Merged

Document restriction on top-level JSON types explicitly #1496

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3c1ce59
Document restriction on top-level JSON types explicitly
verhovsky Apr 11, 2023
b2bcc9a
Update docs/README.md
jkbrzt May 23, 2023
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
2 changes: 2 additions & 0 deletions docs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -912,6 +912,8 @@ http --offline --print=B pie.dev/post \
]
```

Sending scalar JSON types (a single `null`, `true`, `false`, string or number) as the top-level object is impossible using the key/value syntax. But you can still pass it via [`--raw='<value>'`](#raw-request-body).

##### Escaping behavior

Nested JSON syntax uses the same [escaping rules](#escaping-rules) as
Expand Down