-
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: clean up WIP sections for sequence page #2994
Conversation
369b9e2
to
3c5628f
Compare
|
||
- Try and use existing actions | ||
- Implement your own version of built in actions | ||
- Publish reusable actions to npm |
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.
see #3021 for Publish reusable actions to npm
section.
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.
LGTM 👍
Nitpick: can you un-indent the code blocks? (feel free to ignore)
58eabcd
to
e954ef0
Compare
141c450
to
1d1ad0d
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.
@b-admike A few nitpicks otherwise LGTM Good content!
docs/site/Sequence.md
Outdated
argument is typically decorated by @param(). We've made multiple shortcuts | ||
available to the `@param()` decorator in the form of | ||
`@param.<http_source>.<OAI_primitive_type>`. Using this notation, query string | ||
parameters can be described as `@param.query.<OAI_primitive_type>`. Here is an |
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.
typo? I think you mean @param.query.string
=p
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.
Good catch :-). Fixed!
|
||
You can also specify a parameter which is an object value encoded as a JSON | ||
string or in multiple nested keys. For a JSON string, a sample value would be | ||
`location={"lang": 23.414, "lat": -98.1515}`. For the same `location` object, it |
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.
A question: is it meant to be the string value get from the HTTP client?
If we are showing an example value from in the API explorer input field, probably wrap key&value with double quotes.
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.
Actually I took this straight from API explorer and I think they're not wrapped because we define lat/long as number values.
1d1ad0d
to
634291b
Compare
Co-authored-by: Miroslav Bajtoš <[email protected]>
634291b
to
2c63955
Compare
Fixes #2100
Checklist
👉 Read and sign the CLA (Contributor License Agreement) 👈
npm test
passes on your machinepackages/cli
were updatedexamples/*
were updated👉 Check out how to submit a PR 👈