Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "Fix docs for getErrorMessagesIndexedByAttribute - array keys must be strings" #673

Merged

Conversation

arogachev
Copy link
Contributor

Reverts #669

@arogachev arogachev merged commit e1c0866 into master Mar 26, 2024
2 checks passed
@arogachev arogachev deleted the revert-669-Fix-docs-for-getErrorMessagesIndexedByAttribute branch March 26, 2024 12:52
Copy link

what-the-diff bot commented Mar 26, 2024

PR Summary

  • Enforcing Required Attribute Names as Strings
    Previously, the attribute names would accept any data type when used with the Each rule. Going forward, only string types will be accepted as attribute names for each rule, as per this update.

  • Updated Array Input Exception Understanding
    In older versions, the use of non-string keys with top level attributes (like [21, 22, 23, 20]) could result in throwing InvalidArgumentException. This pull request modifies this behaviour inherently by changing such an example from a potential error source to a valued input, producing an output like ['1' => ['Value must be no less than 21.'], '2' => ['Value must be no less than 21.'],].

  • Removal of Specific Documentation Link
    The link dedicated to documentation about usage of keys containing separators or shortcuts, has been removed in this pull request. Please refer to the updated documentation for recent understanding of keys and shortcuts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant