"Not a valid UUID" except it is

Expected behavior

Lookup by UUID should work even if the UUID does not match the official RFC format.

Actual behavior

The front-end refuses the UUID we indeed use in our database, insisting it is “Not a valid UUID”.

Failure Logs

Here is an UUID that works:
And one that doesn’t:

According to the one and only source of knowledge on this planet this is due to the first digit of the third group not being a proper UUID version (6), due to there being only 5 UUID versions.


Please provide any relevant information about your setup.

  • Package Version: ^8.3.3
  • Express Version: 4.17.1
  • Sequelize Version: 6.6.2
  • Database Dialect: MSSQL
1 Like

Hi @kll :wave: to understand where does the problem come from, can you provide me more context please?
Where do you see this error? Come from your backend or directly in the frontend?

Plop @Arnaud_Moncel, it comes from the FA front-end when filtering on an UUID field using the is operator. Here’s a screenshot for context:

Oh right I see, unfortunately we try to support only “standard” things.
I send your request anyway on our product board.
I can suggest you to try to change on your model definition uuid by string.
Let me know.

1 Like