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
Haven't dug into the code enough to know if there's a technical reason behind it, but it seems like extending the type of viewKey from string | undefined to at least string | symbol | undefined would be nice!
Use case here is that I have a well-known shared viewKey I'd like to use (i.e. not a resource ID of any kind) and I like Symbols over constant strings.
The text was updated successfully, but these errors were encountered:
The basic structure is already pretty hard to serialize, so, yeah, kinda tough. Using a string constant seems fine since it's rare you'll share that key outside of your internal application, but if we come up with a good reason to support it, I'm open to PRs!
Haven't dug into the code enough to know if there's a technical reason behind it, but it seems like extending the type of
viewKey
fromstring | undefined
to at leaststring | symbol | undefined
would be nice!Use case here is that I have a well-known shared viewKey I'd like to use (i.e. not a resource ID of any kind) and I like
Symbol
s over constant strings.The text was updated successfully, but these errors were encountered: