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
[Cases] Fix fields query parameter in the _find
API
#128143
Conversation
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/response-ops-cases (Feature:Cases) |
@elasticmachine merge upstream |
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.
Tested and LGTM
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: cc @cnasikas |
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.
nice. Thanks for adding that extra test.
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
I decided to not backport to the previous versions as it is risky and the bug fix is of low importance. |
Summary
If you pass a single value in the
fields
query parameter you get a bad request error. This is happening becauseio-ts
expects an array of strings but if a single value is provided is being provided as a single string. This PR fixes this issue.Checklist
Delete any items that are not applicable to this PR.
For maintainers
Release notes
Fix bug when providing a single value to the
fields
query parameter of the Cases find API.