Nested autoForms in 7.x+

[sylido]

Switching from an earlier version 6.x to 7.x it seems like I have some templates that have a parent +autoForm in them with a specific simple schema associated.

Then a separate template gets used and it nests a second +autoForm with a different simple schema object that gets built dynamically as fields can be added/removed as needed there.

Previously it would automatically merge the data from both autoforms and the schemas as well, it would validate the fields correctly when getting submitted to the backend. Now it seems like I need to manually retrieve the values from the child autoform and merge them to the document of the parent autoform in it's hook to get the same behavior, but I still get problems with the simple schema being used.

Was that a breaking change part of 7.x that wasn't called out specifically as I understand having nested forms is just bad html ?

[github-actions]

Thank you for submitting this issue!

We, the Members of Meteor Community Packages take every issue seriously.
Our goal is to provide long-term lifecycles for packages and keep up
with the newest changes in Meteor and the overall NodeJs/JavaScript ecosystem.

However, we contribute to these packages mostly in our free time.
Therefore, we can't guarantee you issues to be solved within certain time.

If you think this issue is trivial to solve, don't hesitate to submit
a pull request, too! We will accompany you in the process with reviews and hints
on how to get development set up.

Please also consider sponsoring the maintainers of the package.
If you don't know who is currently maintaining this package, just leave a comment
and we'll let you know