Repository navigation
[v2] Port submit metadata support from v1 #2303
Description
Activity
Hi @LeCarbonator, I'd like to take this. My plan, following your notes:
- a default meta on form options, with an optional per-submit override on
handleSubmit onSubmitalways receives the resolved meta- validators get it through a union on the event, so it's typed only for submits
- listeners get it as optional
Is this safe to start on
alphanow, or should it wait for the submission rework / #2306?- a default meta on form options, with an optional per-submit override on
Submit metadata has not yet been implemented in v2. Adding it would allow metadata associated with a submission to remain available throughout the relevant form lifecycle.
Submit metadata should be available in the following places:
onSubmit: Required. The callback should receive the effective metadata, using the per-submission override when provided and the configured default otherwise.Some thoughts
For validators, a discriminated union with a submit event could make the metadata available with stronger type safety only when the event is a submission. Listener metadata should likely remain optional because expressing the same relationship in the shared listener types may be too cumbersome.