-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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.
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
docs: update docs for issue 2208 switching to url-encoded style params #4620
Conversation
f0048bc
to
b837c57
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some grammar related comments.
docs/site/Parsing-requests.md
Outdated
``` | ||
|
||
LoopBack has switched definition of json query params from the `exploded`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change:
LoopBack has switched the definition
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed
docs/site/Parsing-requests.md
Outdated
with `style: "deepObject"` only. Please note that this style does not preserve | ||
encoding of primitive types, numbers and booleans are always parsed as strings. | ||
At the moment, LoopBack supports both url-encoded and exploded values for json | ||
query parameters. Please note that this style does not preserve encoding of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change:
does not preserve the encoding
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed
docs/site/Parsing-requests.md
Outdated
|
||
For example: | ||
For instance, to filter api results from the GET '/todo-list' endpoint in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe just to filter results
(without api
)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed
b837c57
to
0bfaaff
Compare
docs/site/Parsing-requests.md
Outdated
``` | ||
|
||
LoopBack has switched the definition of json query params from the `exploded`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick: how about move this sentence to the beginning of the section?
And I remember there is a breaking change of the syntax, can you explain more about how to upgrade after the release?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry never mind, found the change log in https://github.com/strongloop/loopback-next/blob/master/packages/rest/CHANGELOG.md#breaking-changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to moving this sentence up
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can run npm run lint:fix
from the root folder to fix the lint error.
Otherwise LGTM 👍
docs/site/Parsing-requests.md
Outdated
``` | ||
|
||
LoopBack has switched the definition of json query params from the `exploded`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to moving this sentence up
0bfaaff
to
9236af7
Compare
#2208
Opened to fix #4347 (comment)
Checklist
👉 Read and sign the CLA (Contributor License Agreement) 👈
npm test
passes on your machinepackages/cli
were updatedexamples/*
were updated