-
Notifications
You must be signed in to change notification settings - Fork 102
Open
Labels
Priority: P3May be fixed according to the position in the backlogMay be fixed according to the position in the backlogbuggood first issue
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"
<virtualType name="IowebModuleLockListingDataProvider" type="Magento\Framework\View\Element\UiComponent\DataProvider\SearchResult">
<arguments>
<argument name="resourceModel" xsi:type="string">Ioweb\ModuleIntegration\Model\ResourceModel\Lock\Collection</argument>
<argument name="mainTable" xsi:type="string">ioweb_base_lock</argument>
</arguments>
</virtualType>
<type name="Magento\Framework\View\Element\UiComponent\DataProvider\CollectionFactory">
<arguments>
<argument xsi:type="array">
<item xsi:type="string" name="ioweb_wupexintegration_lock_listing_data_source">IowebModuleLockListingDataProvider</item>
</argument>
</arguments>
</type>
To Reproduce (*)
Steps to reproduce the behavior:
- Create a model triad with the extension
- Try to create a ui component grid for the model triad
- 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.
Metadata
Metadata
Assignees
Labels
Priority: P3May be fixed according to the position in the backlogMay be fixed according to the position in the backlogbuggood first issue