kachick/ruby-ulid

Should accept `O`, `o`, `I`, `i`, `L`, `l`, and `-` in the parser?

kachick opened this issue · 0 comments

ref: ulid/javascript#85, https://www.crockford.com/base32.html, ulid/spec#38

In my understanding, Crockford's base32 does not contain L for the encoded product. So ULID can ignore L

This is my understanding. 🤔
If not, the string based sort oder will be complex?