You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Now we have to copy the full path and then modify this value, and if we copy it from the vendor folder vendor/magento/module-catalog/view/frontend/templates/product/view/form.phtml, we need to open composer.json or etc/module.xml to find out the correct name of the module -> Magento_Catalog::product/view/form.phtml. With Magento modules, everything is simple, but third-party packages are often named differently from the module name.
Describe the solution you'd like (*)
In the context menu of the file (right click), there is an item Copy Path.... It would be very convenient if you add a quick copy of the template, styles, script, etc. paths to this item. So that the new item something like Copy Module/Extension Path immediately copies the value of the type Vendor_Module::path/to/template.phtml.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Now we have to copy the full path and then modify this value, and if we copy it from the vendor folder vendor/magento/module-catalog/view/frontend/templates/product/view/form.phtml, we need to open composer.json or etc/module.xml to find out the correct name of the module -> Magento_Catalog::product/view/form.phtml. With Magento modules, everything is simple, but third-party packages are often named differently from the module name.
Describe the solution you'd like (*)
In the context menu of the file (right click), there is an item Copy Path.... It would be very convenient if you add a quick copy of the template, styles, script, etc. paths to this item. So that the new item something like Copy Module/Extension Path immediately copies the value of the type Vendor_Module::path/to/template.phtml.
The text was updated successfully, but these errors were encountered: