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
Thinking out loud, while having them work with values in the way you show could be used for producing better error messages, malli already handles that part really well so it'd be overlapping functionality.
There also might be cases where it's somewhat ambiguous whether the second value is a schema or an actual value, as the projects I work with tend to have lookup maps from keywords to functions to enable certain dynamic behaviors, especially on frontend side. So maybe having it work with values would be a bit superfluous?
Currently, we have
m/merge
. Instead, we should havemalli.set
with at least:difference
intersection
union
(the currentm/merge
)should these also work with values? e.g:
The text was updated successfully, but these errors were encountered: