You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When dealing with multiple tokens of differing type (hotp/totp/custom (out of scope of OTPAuth)), it'd be good to be able to distinguish them according to type, so that it's easier to perform type specific operations (UI, sorting, etc).
The default would be totp and HMAC tokens would be hotp.
I think it should be easy enough to implement; during URI parsing, add it to config
I admittedly didn't know/check for that, thank you.
Unfortunately, that's more of a check / expression, where I'd rather directly get a property as there's also assumed certainty.
And it feels a little expensive checking that way - but, I have no idea on that!
When dealing with multiple tokens of differing type (hotp/totp/custom (out of scope of OTPAuth)), it'd be good to be able to distinguish them according to type, so that it's easier to perform type specific operations (UI, sorting, etc).
The default would be
totp
and HMAC tokens would behotp
.I think it should be easy enough to implement; during URI parsing, add it to
config
otpauth/src/uri.js
Line 77 in a53054f
And the classes can add it to the defaults.
Can attempt a pull request if you'd like.
The text was updated successfully, but these errors were encountered: