Resource Key in Form Setup for Nested Union Forms

Union forms are pretty complex beasts TBH. There is typically no one resource that can be used to describe them, and the way that it is implemented when using auto?: true is that an updater function is provided, which will dynamically modify the resource/actions depending on the current parameters.

Is there any specific reason you’re building the form specification manually, as opposed to:

AshPhoenix.Form.for_create(
  ParentModule, 
  :create, 
  api: MyDomain.Api, 
  forms: [auto?: true]
)