You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each route has a form. The subresource route is rendered inside an <Outlet /> in the parent route, but it renders its form using a modal control (using shadcn's Dialog), and when I view the resulting HTML, the form from the child route is not nested inside the parent route's form.
However, when I submit the child route's form, I see a POST request for both routes, which I want to avoid. Is this likely the result of the route nesting? If so, is there a way to avoid this behavior?
The <Outlet /> is also wrapped in a <RemixFormProvider> (as well as being inside a <fetcher.Form>)
I am writing this quickly so I can get it out of my head and maybe get someone else to see an obvious answer that I'm missing, but if it would be helpful to make a minimal repro, I can give that a try tomorrow.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a route structure that looks like this:
Each route has a form. The
subresource
route is rendered inside an<Outlet />
in the parent route, but it renders its form using a modal control (using shadcn's Dialog), and when I view the resulting HTML, the form from the child route is not nested inside the parent route's form.However, when I submit the child route's form, I see a POST request for both routes, which I want to avoid. Is this likely the result of the route nesting? If so, is there a way to avoid this behavior?
Other context:
<Outlet />
is also wrapped in a<RemixFormProvider>
(as well as being inside a<fetcher.Form>
)Beta Was this translation helpful? Give feedback.
All reactions