Open mgarciaebo opened 6 years ago
@mgarciaavz, thank you for your report. We've acknowledged the issue and added to our backlog.
I'm working on this #distributed-cd
@mgarciaavz thank you for joining. Please accept team invitation here and self-assign the issue.
Hi @engcom-Delta. Thank you for working on this issue. Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:
[ ] 1. Add/Edit Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[ ] 2. Verify that the issue is reproducible on 2.3-develop
branchDetails
- Add the comment @magento give me 2.3-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.3-develop
branch, please, add the label Reproduced on 2.3.x
.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
[ ] 3. If the issue is not relevant or is not reproducible any more, feel free to close it.
@magento give me 2.3.7-p2 instance
Hi @magedad. Thank you for your request. I'm working on Magento instance for you.
Hi @magedad, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.
It seems that it's impossible to create stand-alone forms using UI Components. I mean, simple forms, not attached to a collection (like the standard import-export forms), because Magento expects for a collection in order to apply filters, and a bunch of other things.
Those kind of forms can still be inserted using blocks and layout injection, as usual, but you encourage us to use UI Components. Actually, classes as Backend\Block\Widget\Form and Backend\Block\Widget\Form\Generic, has been deprecated in favor of UI Component implementation, so it makes no sense that this doesn't work.
Preconditions
Steps to reproduce
Expected result
Actual result