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
Basically would need to have the submit handlers all fall through to whatever the JSX magic attached to the form on behalf of Solid. It looks like createSubmitHandler which wraps all this logic always prevents default no matter what you attach to events or submit handlers. And the default submit handler otherwise cannot be bypassed.
Am I missing something? We would have to useAction our action and call it manually to have actions working here. Which means we are doubling up on the submissions and other tracking that Solid can do with its actions.
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
-
The way the submission handler works here for forms, falling back to a fetch call would seem to override the behavior of assigning a Solid action https://docs.solidjs.com/solid-router/concepts/actions to the form.
Basically would need to have the submit handlers all fall through to whatever the JSX magic attached to the form on behalf of Solid. It looks like
createSubmitHandler
which wraps all this logic always prevents default no matter what you attach to events or submit handlers. And the default submit handler otherwise cannot be bypassed.Am I missing something? We would have to
useAction
our action and call it manually to have actions working here. Which means we are doubling up on the submissions and other tracking that Solid can do with its actions.Beta Was this translation helpful? Give feedback.
All reactions