Implement module name validation in 'Create a plugin' and 'New module' dialog
See original GitHub issueDescribe the bug
To implement module existence validation for the field Target Module
in the following scenarios
- Create a plugin dialog
- Create an observer dialog
- New module dialog
This was implemented in the old way and removed as part of https://github.com/magento/magento2-phpstorm-plugin/pull/324 and https://github.com/magento/magento2-phpstorm-plugin/pull/318, respectively, as its not directly possible using annotations. More info at https://github.com/magento/magento2-phpstorm-plugin/pull/324#discussion_r509635113.
Expected behavior
Target module field is validated using the list of indexed modules in the Magento 2 project
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Change the validation of the Argument Name field in ... - GitHub
Describe the bug. Currently, we can't use an underscore _ in the argument name, only letters and numbers. The underscore character is not ......
Read more >Use the Plug-in Manager in Logic Pro - Apple Support
In Logic Pro, use the Plug-in Manager window to validate, organize, and manage installed plug-ins.
Read more >Plugin Development - Gerrit Code Review
Plugins that use explicit Guice registration must name the Guice modules in the manifest. Up to three modules can be named in the...
Read more >Defining Constraints (Validations) on Entities and/or Fields.
The next step is to create the class that will validate the constraint. The constraint validation will go in the namespace Drupal\[MODULENAME]\ ...
Read more >Displaying content in a dialog in JIRA - Atlassian Developer
Open a command window and go to the plugin root folder (where the pom. · Run atlas-create-jira-plugin-module . · Supply the following information ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I understand @VitaliyBoyko, thanks. In that case, would it be better to create a new rule to validate
target module
fields? It would implement same logic of getting list of modules in current project and checking the existence of the value in the module list, but inside a rule so that annotations can be used and it can be reused.PR is merged (https://github.com/magento/magento2-phpstorm-plugin/pull/358), hence closing.