magento / magento/magento2-phpstorm-plugin
Cannot generate UI component grid based on Model Triad
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 463
- Forks
- 98
- Avg merge
- 1h 6m
- Merged PRs (30d)
- 3
Description
**Describe the bug** (*)
I've generated my model called Lock from the phpstorm plugin.
I'm generating my ui component grid based on the Lock model triad via the ui comonent
Multiple errors arise because the naming is not consistent.
For example
In di.xml
- The name of the virtual type is declared as is, but on the ui component it's expected to be in namespace `Ui\Component\Listing`
- In the resourceModel argument the collection is passed instead of the ResourceModel
- In the arguments list the name is missing `name="collections"`
```
Ioweb\ModuleIntegration\Model\ResourceModel\Lock\Collection
ioweb_base_lock
IowebModuleLockListingDataProvider
```
**To Reproduce** (*)
Steps to reproduce the behavior:
1. Create a model triad with the extension
2. Try to create a ui component grid for the model triad
3. The controller is throwing various errors
**Expected behavior** (*)
The grid is working
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Please complete the following information:** (*)
- OS: Windows 11 x64
- PhpStorm/Intellij version: 2024.2.4
- Plugin Version: 5.3.1
**Additional context**
Add any other context about the problem here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by creating a model triad with the PhpStorm plugin and generating a UI component grid. Inspect the generated di.xml, UI component, and controller errors, checking the virtual type namespace, resourceModel value, and missing collections argument. Done means the generated grid works without the reported errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, php
- Domain
- backend, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100