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
Update API Example in backend to use the new /content/_search endpoint #19691
Comments
So just to be clear, I think we need to add a new example, not replace the existing one. The existing example uses a GET, so it's easy to test from any browser, but I think the _search endpoint is a POST, which requires special tools (like postman). I think it's important that we keep a really easy to use example in there (without the need for a POST). |
In addition, it might also be a good time to think about adding a GraphQL example in there as well. We have alot more customers using this now, so an easy to find example could be really useful for them. |
|
PR: #19705 |
Looking good - a few things |
* #19691 fix A curl example needs to be added to the query dialog in content search portlet. Also the XML information link needs to be removed * Feedback
Passed internal qa |
Fixed, tested on release-21.02 // Postgres // FF |
We need to update this screen to show an example using the new /api/content/_search POST method
The example should display a curl example like:
but with the correct values filled in. Be careful of escaping quotes as well.
Additionally we can remove the link to the xml example and just have the json example link that does the actual post and displays the results, rather than the GET link we have now.
The text was updated successfully, but these errors were encountered: