Support UUID beyond UUIDv4

[tiakun]

I ran into a problem that I got error during enrichment process because my row ID is UUIDv6, which is used as the query parameter in the enrichment function and Sequin could not process it correctly. I am not sure why the code explicitly disallow other UUID versions anyway.

Problem

Currently, in lib/sequin/string.ex line 47, the implementation explicitly checks for info[:version] == 4 and info[:variant] == :rfc4122. This restricts UUID acceptance to only version 4 (UUIDv4), excluding other valid UUID versions.

Suggestion

To increase flexibility and compatibility, it would be helpful to support additional UUID versions (such as v1, v3, v5, etc.) as long as they conform to the RFC 4122 variant. This would allow a broader set of valid UUIDs to be accepted and processed.

Reference

• lib/sequin/string.ex#L47

Expected Outcome

• Accept and process UUIDs of versions other than v4, provided they are RFC 4122 compliant.

---

Let me know if you need further clarification or examples!

[yakivy]

@RTLS and @davoclavo, could you take a look please? It blocks one of our use cases too.
As I understand fix should be trivial (just to remove version check), but it would be great to have validation from your side.
Let me know if you need any help.