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
This applies to CredentialCreate, CredentialAccept, and CredentialDelete transaction views, as well as anywhere else Credential details are displayed (currently I think that's all).
Similar to how the explorer decodes other hex values like accounts' Domain value or extended currency codes, I expect the CredentialType field to be decoded into human-readable text, at least if it decodes into reasonable plain text using ASCII. (Or UTF-8, although that has a lot more edge cases to account for.) Obviously you would want to exclude or escape special characters so that you don't end up with cross-site scripting, or right-to-left text, or other glitchiness, similar to how you do with Domains, Memos, and other examples.
I would expect this to display the CredentialType as test_cred1 for example. (Test transaction on Devnet):
The text was updated successfully, but these errors were encountered:
This applies to CredentialCreate, CredentialAccept, and CredentialDelete transaction views, as well as anywhere else Credential details are displayed (currently I think that's all).
Similar to how the explorer decodes other hex values like accounts'
Domain
value or extended currency codes, I expect theCredentialType
field to be decoded into human-readable text, at least if it decodes into reasonable plain text using ASCII. (Or UTF-8, although that has a lot more edge cases to account for.) Obviously you would want to exclude or escape special characters so that you don't end up with cross-site scripting, or right-to-left text, or other glitchiness, similar to how you do with Domains, Memos, and other examples.I would expect this to display the CredentialType as
test_cred1
for example. (Test transaction on Devnet):The text was updated successfully, but these errors were encountered: