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
The default en translations for max have a strange construct (possibly a typo) for slices.
Expected:
{0} must contain maximum {1} items
Actual:
{0} must contain at maximum {1} items
Possibly this is attempting {0} must contain a maximum {1} items or {0} must contain at most {1} items. Not sure what the intent is, but the actual isn't right..
Since the equivalent with min resolves to {0} must contain at least {1} items, I'm pretty sure the intent here was to have {0} must contain at most {1} items as its max counterpart.
Package version eg. v9, v10:
v10
Issue, Question or Enhancement:
The default en translations for
max
have a strange construct (possibly a typo) for slices.Expected:
Actual:
Possibly this is attempting
{0} must contain a maximum {1} items
or{0} must contain at most {1} items
. Not sure what the intent is, but the actual isn't right..Code sample, to showcase or reproduce:
Hook up the default en translations and you'll get
URIs must contain at maximum 5 items
The text was updated successfully, but these errors were encountered: