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
equals-field relies on a new agreement: multiple selectors!
Unfortunately, this is not supported by translate-errors, which assumes that you've gone through attr
I imagine the solution would be to make a selector be run against a "map-if-vector" in translate-errors or enforce that all selectors must be a list, and then update the translation for equals-field to pull first-selector and second-selector from the vector
Alternatively, any key matching *selector (or that's in a supplied vector?) could be translated, that could work too... and would allow for multiple in a different sense (I could equals-field to any field)
The text was updated successfully, but these errors were encountered:
Let's try again with the actual issue I am seeing, because I've misreported.
assign-names doesn't work for the various different selector fields provided (:selector, :first-selector, etc.) I propose that we come up with a way to support these various selector fields!
I've got my own alternative implementation of assign-names, I've used a slightly different style to yours, but I'm still not happy with my implementation.
equals-field
relies on a new agreement: multiple selectors!Unfortunately, this is not supported by translate-errors, which assumes that you've gone throughattr
I imagine the solution would be to make a selector be run against a "map-if-vector" intranslate-errors
or enforce that all selectors must be a list, and then update the translation forequals-field
to pull first-selector and second-selector from the vectorAlternatively, any key matching *selector (or that's in a supplied vector?) could be translated, that could work too... and would allow for multiple in a different sense (I could equals-field to any field)The text was updated successfully, but these errors were encountered: