magento / magento/catalog-storefront
Handle missed GQL fields for CMS category block
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 7
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Description (*)
As a merchant I want storefront API for CMS category block to be efficient, so I can have performant GraphQL API.
For now the \Magento\CatalogCmsGraphQl\Model\Resolver\Category\Block resolver used. But we need to store CMS category block in elasticsearch.
Current Graph Ql schema defined in the \Magento\CmsGraphQl\Model\Resolver\DataProvider\Block PHP class:
BlockInterface::BLOCK_ID => $block->getId(),
BlockInterface::IDENTIFIER => $block->getIdentifier(),
BlockInterface::TITLE => $block->getTitle(),
BlockInterface::CONTENT => $renderedContent,
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 Magento\CmsGraphQl\Model\Resolver\DataProvider\Block and compare its current GraphQL fields with the CMS category block resolver and Elasticsearch requirements described in the issue. Trace how the block data is exposed and stored, then verify that the required fields are available through the storefront API and Elasticsearch-backed path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, graphql, php
- Domain
- api, backend, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100