Unit Test of Base32 implementation

[jetpack-io]

Unit Test of Base32 implementation

[ongteckwu]

My output for the test case for the typescript implementation https://github.com/ongteckwu/typeid-ts matches this repo's.

[loreto]

@alisa101rs Thanks for reporting.

I ran two tests:

1. I tried the encoding using ulid (which uses the same alphabet), it matched
2. I tried the encoding using gos standard base32 library, but with the custom alphabet ... it did not match.

So there's a discrepancy between the two approaches. I'm doing some more testing to determine what should be the "right" way to encode typeids and will clarify the spec. I'll circle back.

[loreto]

OK, I did a bunch of testing, and I think the original implementation in this repo is still correct.

In particular the current implementation aligns the encoding of the typeid in an intuitive way with UUIDs. So that,
the typeid prefix_00000000000000000000000001 corresponds to the UUID 00000000-0000-0000-0000-000000000001. I added a test to check for that here: https://github.com/jetpack-io/typeid-go/blob/main/typeid_test.go#L100

Note that the standard base32 algorithm works in groups of 5 bytes, and therefore is subject to add padding at the end
of the byte array one is trying to decode. In our case though, we use an algorithm without padding that works byte by byte; to make the standard base32 algorithm work, padding would have to be added to the front of the array.
I added a test to validate that here: https://github.com/jetpack-io/typeid-go/blob/main/base32/base32_test.go#L11