I've updated the code to use the new ts-ucans library.
I admit I've done it somewhat hacky - e.g. we're UCAN.validateing twice: In ucans.ts there's both decode and validate. Ideally you'd only need validate, and never decode, as anytime you're using decode you could've also just also validated, and that's what we're doing afterwards most of the time anyway.
Another thing I've tackled in this PR is #10.
Now, I'm just grouping multiple attenuations into a single column.
It still disappears when there's no attenuation, but I now actually think that's not an issue. I get that the idea is to explain what's there, not what could be there.
But yeah, I fixed that it shows the attenuation multiple times, if there are multiple :)
I've updated the code to use the new ts-ucans library.
I admit I've done it somewhat hacky - e.g. we're
UCAN.validateing twice: Inucans.tsthere's bothdecodeandvalidate. Ideally you'd only needvalidate, and neverdecode, as anytime you're usingdecodeyou could've also just alsovalidated, and that's what we're doing afterwards most of the time anyway.Another thing I've tackled in this PR is #10. Now, I'm just grouping multiple attenuations into a single column.
It still disappears when there's no attenuation, but I now actually think that's not an issue. I get that the idea is to explain what's there, not what could be there.
But yeah, I fixed that it shows the attenuation multiple times, if there are multiple :)