Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have a scenario where I need to test an ID not knowing before hand if is a valid Sqid or not, and, in some cases when an ID looks valid, but results in elements bigger than the maximum u64 value, the
decode()
function panics! For example, with the ID0J4AEXRN106Z0
.To fix this I made
to_number()
return anOption<u64>
(instead of justu64
), and only push the value ondecode()
in case ofSome()
.By the way, I’m adding support to Sqids to an upcoming version of my ID parser/debug CLI tool, have a look: https://github.com/racum/uuinfo