Issue #35691 Make UI Components Form "templates/form/collapsible" default value for "template"

[artskirk]

If you forget to include the "template" item in the "data" argument, you'll get an infinite spinner.
Example: Edit this file app/code/Magento/Catalog/view/adminhtml/ui_component/category_form.xml, and make the comment on line number 14

Description (*)

I have added the default configuration: app/code/Magento/Ui/view/adminhtml/ui_component/etc/definition.xml
where I have specified the "template" item with a default value of "templates/form/collapsible"

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes Make UI Components Form "templates/form/collapsible" default value for "template" and/or give better errors #35691

Manual testing scenarios (*)

1. Edit this file app/code/Magento/Catalog/view/adminhtml/ui_component/category_form.xml, and make the comment on line number 14
2. Run bin/magento c:f
3. Navigate to category page in admin panel.

Expected result
The category page is available, no infinite spinner appears.

Questions or comments

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @artskirk. Thank you for your contribution
Here are some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

For more details, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel