-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Uid] isValid fails when passing non Rfc4122 IDs #57398
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
Comments
I understand that you want to validate UIDs in representations other than RFC 4122, but the fact that the |
well depends on how you look at it, since it's not saying it has to be RFC 4122 anywhere but yeah, if you look at it like that it's a feature request to extend |
related: #51540 |
…traint to allow accepting different ULID formats (alexandre-daubois) This PR was merged into the 7.2 branch. Discussion ---------- [Validator] Add the `format` option to the `Ulid` constraint to allow accepting different ULID formats | Q | A | ------------- | --- | Branch? | 7.2 | Bug fix? | no | New feature? | yes | Deprecations? | no | Issues | - | License | MIT Related to #51540 and #57398 Commits ------- 880e8fa [Validator] Add the `format` option to the `Uuid` constraint to allow accepting different ULID formats
Symfony version(s) affected
7.1.1
Description
When trying to validate UUIDs in a format that's not Rfc4122 it'll always fail.
How to reproduce
Possible Solution
The
isValid
seems to contain a regex that checks for the Rfc4122 structure, probably should be expanded to check the other representations as well.Additional Context
No response
The text was updated successfully, but these errors were encountered: