Open kachick opened 3 years ago
Hi! I'm writing a new Ruby library for handling ULID in these days. Now I’m testing other implementations examples in https://github.com/kachick/ruby-ulid/issues/53
And I have found weird examples in this original repository.
000XAL6S41ACTAV9WEVGEMMVR8 looks weird example from 2 reasons.
000XAL6S41ACTAV9WEVGEMMVR8
L
Crockford's base32
1
Returned values from current npm version looks correct.
npm
$ node -v v14.16.0 $ npm list ulid@2.3.0 /Users/kachick/repos/ulid-javascript
const ULID = require('ulid') mf = ULID.monotonicFactory() mf(150000) // 0000004JFG7NP20TJP26ZJDASS mf(150000) // 0000004JFG7NP20TJP26ZJDAST mf(150000) // 0000004JFG7NP20TJP26ZJDASV mf(150000) // 0000004JFG7NP20TJP26ZJDAST mf(150000) // 0000004JFG7NP20TJP26ZJDASW mf(150000) // 0000004JFG7NP20TJP26ZJDASX mf(100000) // 0000004JFG7NP20TJP26ZJDASY
Hi! I'm writing a new Ruby library for handling ULID in these days. Now I’m testing other implementations examples in https://github.com/kachick/ruby-ulid/issues/53
And I have found weird examples in this original repository.
000XAL6S41ACTAV9WEVGEMMVR8
looks weird example from 2 reasons.L
in the encoded string. In my understanding,Crockford's base32
does not containL
for the encoded product. So ULID can ignoreL
, Is this correct understanding? ref: https://github.com/ulid/spec/issues/38, https://github.com/kachick/ruby-ulid/issues/57L
as1
.Returned values from current
npm
version looks correct.