-
Notifications
You must be signed in to change notification settings - Fork 1.8k
No developer level documentation on how to programmatically (in code) create a custom attribute input type #9452
No developer level documentation on how to programmatically (in code) create a custom attribute input type #9452
Comments
Hi @rparsi-boxycharm. Thank you for your report. Add a comment to assign the issue:
|
@keharper Will a new menu page inside https://experienceleague.adobe.com/docs/commerce-admin/catalog/product-attributes/product-attributes.html be OK? Right after 'Add attribute to a product' I could add a page 'Create a custom attribute input type'. Will it belong there? |
@goivvy, I'll defer to @keharper, but I don't think that the Admin User Guide is the right place for developer tutorials. I think this would make more sense as a tutorial in the PHP Developer Guide. What do you think? |
@jeff-matthews I agree. @magento I am working on this |
@goivvy I had forgotten there was a tutorials section in the PHP Developer Guide and was looking for a place under "Component Development" to insert the info requested in this issue. The tutorial section would be perfect. Please consider adding links in EAV and extension attributes or anywhere else to your new tutorial. |
@keharper OK. I'm still working on it. |
@keharper @jeff-matthews What repository should I send a PR to? magento/devdocs? |
@goivvy created a new topic to address your request in AdobeDocs/commerce-php#150. Could you please take a look and share your feedback? |
This repository is not supported anymore. |
Is there an existing issue for this?
What's missing?
I've searched the available magento developer documentation regarding attribute input types.
Specifically I'm looking for developer docs illustrating how to create a custom attribute input type in code,
that can be used as the renderer for (also in code) custom entity attributes.
For example, how to extend
Magento_Ui/js/dynamic-rows
to create a new custom attribute input type with custom rendering.The text was updated successfully, but these errors were encountered: