[GraphQl] Excluding the disabled parent category from the category breadcrumbs

[eduard13]

Description (*)

This PR excludes the disabled parent category from the category's breadcrumbs, as the category won't be available on clicking on it.

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes [Atwix]products query returns breadcrumb data for categories whose parent category is disabled #30468

Manual testing scenarios (*)

1. Create the following tree: Category 1 / Category 1.1 / Category 1.2
2. Disable the Category 1.1
3. Run the following query to get the breadcrumbs for Category 1.2

categoryId = Category 1.2 ID

{
  category(id: <categoryId>) {
    name
    breadcrumbs {
        category_name
    }
  }
}

Expected Result

{
  "data": {
    "category": {
      "name": "Category 1.2",
      "breadcrumbs": [
        {
          "category_name": "Category 1"
        }
      ]
    }
  }
}

Questions or comments

As an alternative, we may try to add a new attribute for Breadcrumb type , in order to mark the breadcrumb as enabled/disabled.

magento2/app/code/Magento/CatalogGraphQl/etc/schema.graphqls

Lines 264 to 270 in a1e5689

	type Breadcrumb @doc(description: "Breadcrumb item."){
	category_id: Int @doc(description: "Category ID.")
	category_name: String @doc(description: "Category name.")
	category_level: Int @doc(description: "Category level.")
	category_url_key: String @doc(description: "Category URL key.")
	category_url_path: String @doc(description: "Category URL path.")
	}

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @eduard13. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[eduard13]

@magento run all tests

[gabrieldagama]

@magento run all tests

[coderimus]

@magento run Functional Tests B2B

[coderimus]

@magento run Functional Tests CE

[coderimus]

@magento run Functional Tests B2B

[coderimus]

Hello @eduard13 ,
Thank you for the provided changes. 👍 Approve from my side. Let's wait for others review.

[magento-engcom-team]

Hi @coderimus, thank you for the review.
ENGCOM-8386 has been created to process this Pull Request
✳️ @coderimus, could you please add one of the following labels to the Pull Request?

Label	Description
Auto-Tests: Covered	All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered	Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required	Changes in Pull Request does not require coverage by auto-tests

[magento-engcom-team]

Hi @rogyar, thank you for the review.
ENGCOM-8386 has been created to process this Pull Request

[m2-assistant]

Hi @eduard13, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.