This repository was archived by the owner on Nov 19, 2024. It is now read-only.
GraphQL: Add layered navigation documentation #5222
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
keharper
added
Internal Dev
keharper
added
Major Update
…ayered-navigation
…ayered-navigation
…ayered-navigation
…ayered-navigation
erikmarr
reviewed
Sep 11, 2019
cherdman
suggested changes
Sep 11, 2019
| - `FilterMatchTypeInput` - Specify this data type when the the **Catalog Input Type for Store Owner** field for your custom attribute is set to Text Field or Text Area. Your filter must contain the `match` attribute, which will return all items that exactly match the specified string. | ||
| - `FilterRangeTypeInput` - Specify this data type when the the **Catalog Input Type for Store Owner** field for your custom attribute is set to Price or Date. Your filter can contain one or both of the `to` and `from` attributes, which serve to provide a range of values to filter on. | ||
|
|
||
| ## Example |
There was a problem hiding this comment.
This is a great example. Does it make sense to create examples for the other filter types, as well? (FilterMatchTypeInput and FilterRangeTypeInput)
| ``` | ||
|
|
||
| {:.bs-callout-info} | ||
| The `or` attribute cannot be used in a `products` query. Logical OR searches are no longer supported. |
There was a problem hiding this comment.
Interesting. I could see this being a challenge for users to migrate their queries. Is there an alternative to using or that could provide similar results? For example, must and should in Elasticsearch?
| ``` | ||
|
|
||
| {:.bs-callout-info} | ||
| Wildcards are no longer supported in `products` queries. |
There was a problem hiding this comment.
In the absence of wildcards, how can users modify their products queries? Maybe some examples, alongside these callouts, would help (if it makes sense).
Co-Authored-By: Erik Marr <45772211+erikmarr@users.noreply.github.com>
keharper
added a commit
that referenced
this pull request
Oct 8, 2019
* update deprecated description * Revert "update deprecated description" This reverts commit c9b39a0. * GraphQL: update description of deprecated directive (#5213) * update deprecated description * review comments * MC-19250: The stuck deployment on the Cloud because of consumers (#5289) * MC-19250: The stuck deployment on the Cloud because of consumers * Update _includes/config/consumers.md Co-Authored-By: Margaret Eker <meker@adobe.com> * GraphQL: Add layered navigation documentation (#5222) * add filtering example * checkpoint * checkpoint * checkpoint * checkpoint * checkpoint * checkpoint * checkpoint * checkpoint * checkpoint * linting errors * fix link * update opening sentence * remove bogus commit * Apply suggestions from code review Co-Authored-By: Erik Marr <45772211+erikmarr@users.noreply.github.com> * change code gates * final review comments * deprecation notices (#5413) * review draft (#5426) * GraphQL: Add fields and example showing cart rule discounts (#5425) * review draft * minor tweaks * review comment * update example * MC-18725: Write article with clarification of how to use this functionality * MC-18725: Write article with clarification of how customer data works * MC-18725: Write article with clarification of how customer data works * Small grammar changes. * GraphQL: Update pricing schema changes (#5512) * checkpoint * checkpoint * minor updates * review comments * one more review comment * more review comments * correct linting error * remove stray character from TOC * Add store name to store config query schema (#5448) * GraphQL: Add categoryList query (#5562) * checkpoint * review draft * fix linting errors * add to list of cached queries * update example to show usage of * clarify match filters * Apply suggestions from code review Added review comments Co-Authored-By: Jeff Matthews <matthews.jeffery@gmail.com> * update sample * rename file * review comment from Dan * developer feedback * resolve more merge conflicts * linting errors * linting errors
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this pull request
This pull request (PR) updates the
productsquery to include a sample that shows a custom attribute being used to produce results that include layered navigation.Affected DevDocs pages
whatsnew
Added the topic Filtering with custom attributes to the GraphQL Developer Guide and significantly revised the
productsquery to reflect changes in how the query works in Magento 2.3.4.