-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Conversation
An admin must run tests on this PR before it can be merged. |
Hi @pmarjan Thanks for your contribution! The red 'x's above note a couple issues: First, please sign the new Adobe CLA so we can get this merged. Second, you have some markdown errors. Click the Details link above to see them. When using unordered lists, there should be two spaces between the * and the text. This is so it aligns the same way as ordered lists. And if each version is identical, consider symlinking them. For API call examples, please use ```http. |
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.
I've committed some changes for grammar, style, and linting. Please pull them in to your local branch and address the remaining comments. I'll have some follow-up questions, but we need to take care of the basics first.
If you're with a partner that isn't showing up in the list yet, add the company name and URL to the contributor_name/_link lines. Otherwise, include your name and a link to your GitHub account or professional website.
On the surface, the v2.2 and v2.3 versions of the file look the same. If they are, delete the v2.3 version and replace it with a symlink to the v2.2 version. If they're different, apply the changes I made to the v2.2 to the v2.3 version as much as possible.
_data/toc/rest-api.yml
Outdated
@@ -54,6 +54,9 @@ pages: | |||
- label: Search using REST | |||
url: /rest/performing-searches.html | |||
|
|||
- label: Search using /search endpoint |
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.
- label: Search using /search endpoint | |
- label: Search with the /search endpoint |
guides/v2.2/rest/search-endpoint.md
Outdated
``` | ||
GET {{URL}}rest/V1/search?searchCriteria[requestName]=quick_search_container& | ||
searchCriteria[filter_groups][0][filters][0][field]=search_term& | ||
searchCriteria[filter_groups][0][filters][0][value]=Shirt |
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.
Shirt
doesn't look correct here.
guides/v2.2/rest/search-endpoint.md
Outdated
--- | ||
|
||
By using `GET {{URL}}rest/V1/search`, you can search through the catalog. The obtained results will come from your configured search engine (**Stores** > Settings > **Configuration** > **Catalog** > **Catalog Search** > **Search engine**). | ||
This means you can collect results from Elasticsearch, for example, that are very similar to the results that are visible by using the regular frontend search. |
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.
I would not be strict here to which engine is used even as example, maybe better to write
"This means you can collect results from search engine that is enabled. And those results will be equal to the results that are coming by using the regular frontend search."
Hi @pmarjan, thank you for your contribution! |
Sorry, I closed and re-open PR cause I added Marjan to comwrap team and wanted that system recognised that |
I don't know how to push filesystem changes, so I have to just give instructions on setting up a symlink from 2.2 to 2.3.
I've been testing your examples and have some further comments. I'll try to add them by Monday. |
Also, this PR should probably be rebased to |
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.
Looks good for me. Lets wait for some comments from @keharper
57c478b
to
262cc47
Compare
@keharper |
This topic needs some information about when you'd use
Provide descriptions of the 3 search types. |
guides/v2.2/rest/search-endpoint.md
Outdated
The basic usage is: | ||
|
||
```http | ||
GET <host>/rest/<store_code>/V1/search?searchCriteria[requestName]=quick_search_container& |
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.
I tried this query, except I used name
as the search term. The name
attribute is set to Use in Search is set to Yes. Based on the statement in line 8, I would expect the search to work. catalog_view_container
doesn't work either, but advanced_search_container
does.
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.
I think it is like this:
The field
can be set to be search_term
only in the quick_search_container
. This means both catalog_view
and advanced
will not work in that case.
Please send the queries you use? I could check them.
I have now made new version where there is an attempt to outline some differences between the search types, but also between using the v1/search and v1/products. At the end small summary is added too. |
@pmarjan These are some nice additions. I'm going to move things around a bit, but hopefully we can get this to its final state by tomorrow. |
@keharper |
@pmarjan I forgot to tag you and ask for you to review my changes. Since you've done that, you're done. Thanks! |
running tests |
running tests |
running tests |
Hi @pmarjan, thank you for your contribution! |
Using the /search endpoint
whatsnew
Added the Search for products with the /search endpoint topic.