-
-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
UUID matcher throws error for NIL uuid #203
Comments
hmm because it's not valid uuid? Can you be more precise and tell me what kind of error and what is the behavior that you expect? |
it is valid uuid for sure. look at RFC https://tools.ietf.org/html/rfc4122#section-4.1.7 |
No, it's not valid uuid because you can't generate it - it's special type of uuid and I would like to understand the use case in which matcher should support if you expect from me to fix it. |
I really can't find the place in RFC where it is written that NIL uuid is not valid uuid to be honest.
|
I would recommend you to not use NIL uuid and just generate one instead because like I said, it's not type of UUID that can be generated (you won't get it from any api). |
I'am using NILs for a long time for for testing purposes without any false positives and so on. For now case is not crucial for me. Maybe later when I would have some free time |
maybe but it's not a valid scenario that would make me to invest my private time to fix "bug" that affects only wrong usages of the UUID. |
Hi. This just bit me when matching some data in my JSON documents. We use a NIL UUID as a perfectly valid UUID which denotes a root of a tree of some data and PHP Matcher cannot work with it when using |
for uuid
00000000-0000-0000-0000-000000000000
it is throwing an errorThe text was updated successfully, but these errors were encountered: