#40213 - Handle no entity exception for attribute set

[rbaransii]

Logical improvement for edit attribute set entity

Description (*)

Pull request contain exception handling for attribute set entity. When controller can't find entity for attribute set, code catch this runtime moment, set relevant moment and redirect to default attribute set page

Manual testing scenarios (*)

Please sign-in to admin panel next go to Stores > Attributes > Attribute Set

1. Open Default attribute set
2. Change parameter in url to non existing attribute set eg. 85
3. You should be redirected to default attribute set page with relevant message

### Contribution checklist (*) * [x] Pull request has a meaningful description of its purpose * [x] All commits are accompanied by meaningful commit messages * [x] All new or changed code is covered with unit/integration tests (if applicable) * [x] README.md files for modified modules are updated and included in the pull request if any [README.md predefined sections](https://github.com/magento/devdocs/wiki/Magento-module-README.md) require an update * [x] All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @rbaransii. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ 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
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[rbaransii]

@magento assign @magento-engcom-team

[rbaransii]

@magento run Functional Tests B2B

[rbaransii]

@magento run Functional Tests CE

[rbaransii]

@magento run Functional Tests EE

[rbaransii]

@magento run Functional Tests CE

[rbaransii]

@magento run Functional Tests CE

[rbaransii]

@magento run Functional Tests EE

[rbaransii]

@magento run Functional Tests B2B

[rbaransii]

@magento run Functional Tests CE

[rbaransii]

@magento run Functional Tests EE

[rbaransii]

@magento run Functional Tests B2B

[rbaransii]

@magento run Functional Tests EE

[rbaransii]

@magento run Functional Tests B2B

[rbaransii]

@magento run Functional Tests CE

[rbaransii]

@magento run Functional Tests B2B

[rbaransii]

@magento run Functional Tests EE

[magento-automated-testing]

Failed to run the builds. Please try to re-run them later.

[rbaransii]

@magento run Functional Tests CE

[magento-automated-testing]

Failed to run the builds. Please try to re-run them later.

[magento-automated-testing]

Failed to run the builds. Please try to re-run them later.

[engcom-Bravo]

Hi @rbaransii,

Thank you for your contribution! The Magento core engineering team is working on the issue which you have addressed in this PR. Team will cherry pick the commits from your PR and may do further implementation to cover few more scenarios as needed. We will reach out to you if we need more information. For now, you can pause work on this PR. Thank you once again!