Skip to content

[Forwardport] Display a more meaningful error message in case of misspelt module name #13731

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

Merged
merged 6 commits into from
Feb 21, 2018
Merged

[Forwardport] Display a more meaningful error message in case of misspelt module name #13731

merged 6 commits into from
Feb 21, 2018

Conversation

nmalevanec
Copy link
Contributor

Original Pull Request

#12843

Description

Displays a more meaningful error message in case of misspelt module name.

[LogicException] Component 'VendorA_ModuleB' of type '' is not correctly registered.
instead of
[Magento\Framework\Exception\FileSystemException] The file "/composer.json" doesn't exist

Manual testing scenarios

  1. Create a new module and misspell its name in "registration.php" (e.g., 'Vendora_Popup' while the directory is named 'Vendora/Popups').
  2. Run bin/magento module:disable Magento_Bundle (or bin/magento module:enable Magento_Bundle, if it is disabled); yes, it does not have to be the same incorrectly configured module, any will do.
  3. You'll get the mentioned error.

Jānis Elmeris and others added 6 commits February 19, 2018 13:47
@ihor-sviziev
Copy link
Contributor

Hi @nmalevanec your changes looks good for me. Also I see that you covered these changes with unit test (that was missing in 2.2-develop branch). Could you create separate PR to 2.2-develop branch with adding test?

@ihor-sviziev ihor-sviziev self-assigned this Feb 19, 2018
@magento-engcom-team
Copy link
Contributor

Hi @ihor-sviziev, thank you for the review.
MAGETWO-88018 has been created to process this Pull Request

@nmalevanec
Copy link
Contributor Author

@ihor-sviziev, done. #13740

@ihor-sviziev
Copy link
Contributor

@nmalevanec thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants