Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure that url suffix resolvers return strings to match function declaration #30910

Conversation

aligent-lturner
Copy link
Contributor

Description (*)

This pull request is to fix #30909 - where a null value for the product and/or category url suffix results in a type error being thrown during GraphQL queries

Fixed Issues (if relevant)

  1. Fixes ProductUrlSuffix and CategoryUrlSuffix GraphQL resolvers fail with null values #30909

Manual testing scenarios (*)

  1. Clear product and category url suffix values in admin and save
  2. Run GraphQL query that requests product and/or category url suffix value

Questions or comments

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
Copy link

m2-assistant bot commented Nov 13, 2020

Hi @aligent-lturner. 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

@m2-community-project m2-community-project bot added Progress: pending review Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Nov 13, 2020
@sidolov sidolov added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Nov 13, 2020
@aligent-lturner
Copy link
Contributor Author

@magento run all tests

@engcom-Alfa
Copy link
Contributor

engcom-Alfa commented Nov 20, 2020

✔️ QA Passed

Manual testing scenario:

  1. Go to Admin -> Stores -> Configuration -> Catalog -> Catalog -> Search Engine Optimization
  2. Clear product and category url suffix values in admin and save

Screenshot from 2020-11-20 15-24-20

Run GraphQL query that requests product and/or category url suffix value

For Categories:

{
  categoryList {
    url_suffix
  }
}

Before: ✖️ Query fails

Screenshot from 2020-11-20 15-29-15

✖️ with the following error in exception.log:

2020-11-20 13:29:04] main.ERROR: Return value of Magento\CatalogUrlRewriteGraphQl\Model\Resolver\CategoryUrlSuffix::getCategoryUrlSuffix() must be of the type string, null returned {"exception":"[object] (GraphQL\\Error\\Error(code: 0): Return value of Magento\\CatalogUrlRewriteGraphQl\\Model\\Resolver\\CategoryUrlSuffix::getCategoryUrlSuffix() must be of the type string, null returned at /var/www/html/magento24/vendor/webonyx/graphql-php/src/Error/Error.php:174, TypeError(code: 0): Return value of Magento\\CatalogUrlRewriteGraphQl\\Model\\Resolver\\CategoryUrlSuffix::getCategoryUrlSuffix() must be of the type string, null returned at /var/www/html/magento24/app/code/Magento/CatalogUrlRewriteGraphQl/Model/Resolver/CategoryUrlSuffix.php:80)"} []

After: ✔️ Empty string(' ')is returned for url_suffix value

Screenshot from 2020-11-20 15-40-01

It was also checked when the product and category url suffix values were filled

Screenshot from 2020-11-20 15-46-24

Actual Result: ✔️ The correct value is returned for url_suffix

Screenshot from 2020-11-20 15-47-51

For Products:

Run GraphQL query that requests product and/or category url suffix value

{
 products(filter: {sku: {in: ["Simple 1"]}}, sort: {name: ASC}) {
    items {
      url_suffix}
}
}

Before: ✖️ Query fails

Screenshot from 2020-11-20 16-07-11

✖️ with the following error in exception.log:

[2020-11-20 14:07:10] main.ERROR: Return value of Magento\CatalogUrlRewriteGraphQl\Model\Resolver\ProductUrlSuffix::getProductUrlSuffix() must be of the type string, null returned {"exception":"[object] (GraphQL\\Error\\Error(code: 0): Return value of Magento\\CatalogUrlRewriteGraphQl\\Model\\Resolver\\ProductUrlSuffix::getProductUrlSuffix() must be of the type string, null returned at /var/www/html/magento24/vendor/webonyx/graphql-php/src/Error/Error.php:174, TypeError(code: 0): Return value of Magento\\CatalogUrlRewriteGraphQl\\Model\\Resolver\\ProductUrlSuffix::getProductUrlSuffix() must be of the type string, null returned at /var/www/html/magento24/app/code/Magento/CatalogUrlRewriteGraphQl/Model/Resolver/ProductUrlSuffix.php:80)"} []
After: ✔️ Empty string(' ')is returned for url_suffix value

Screenshot from 2020-11-20 16-09-00

@engcom-Alfa engcom-Alfa added the QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope label Nov 20, 2020
@engcom-Charlie
Copy link
Contributor

@magento run all tests

@engcom-Charlie
Copy link
Contributor

@magento run Integration Tests, Functional Tests B2B

@aligent-lturner
Copy link
Contributor Author

@magento run Functional Tests B2B

@m2-assistant
Copy link

m2-assistant bot commented Dec 10, 2020

Hi @aligent-lturner, 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.

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Component: CatalogUrlRewriteGraphQl Partner: Aligent Consulting partners-contribution Pull Request is created by Magento Partner Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ProductUrlSuffix and CategoryUrlSuffix GraphQL resolvers fail with null values
5 participants