magento / magento/catalog-storefront
Handle missed GQL fields: price_range
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 7
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Overridden by "Deprecated resolver" fields should be covered by Storefront API. And depreciation logic should be removed
Field:
`price_range`
GQL scheme:
```
interface ProductInterface @typeResolver(class: "Magento\\CatalogGraphQl\\Model\\ProductInterfaceTypeResolverComposite") @doc(description: "The ProductInterface contains attributes that are common to all types of products. Note that descriptions may not be available for custom and EAV attributes.") {
price_range: PriceRange! @doc(description: "A PriceRange object, indicating the range of prices for the product") @resolver(class: "Magento\\CatalogGraphQl\\Model\\Resolver\\Product\\PriceRange")
}
```
Overridden in:
app/code/Magento/CatalogStorefrontGraphQl/etc/di.xml
`
`
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ProductInterface GQL schema and the price_range field, then inspect the preference in app/code/Magento/CatalogStorefrontGraphQl/etc/di.xml and the Deprecated/PriceRange resolver it names. Done means the price_range field is covered by the Storefront API and the deprecated resolver logic is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100