00694 display both raw and b64-decoded values of memo when relevant

[svienot]

Description:

In AccountDetails and ContractDetails views, when we find that the memo is candidate to Base64 decoding, we now show both the raw value and the decoded value. So if the value is, in fact, not encoded, it is still legible.

This happens only in case the value has not been interpreted (as a URL, an IPFS hash...) since that would mean we were indeed not confused about the encoding.

Related issue(s):

Fixes #694

Notes for reviewer:

Visible on staging server.
Examples:

• actual B64 encoding
• not a B64 encoding

Checklist

• Documented (Code comments, README, etc.)
• Tested (unit, integration, etc.)

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	87.49%	33160 / 37902
🔵	Statements	87.49%	33160 / 37902
🔵	Functions	66.86%	819 / 1225
🔵	Branches	83.64%	3676 / 4395

File Coverage

File	Stmts	% Branch	% Funcs	% Lines	Uncovered Lines
Changed Files
src/components/values/BlobValue.vue	90.9%	76.92%	100%	90.9%	30, 35, 110-115, 122-126, 147-148, 160-161
src/pages/AccountDetails.vue	95.37%	82.79%	100%	95.37%	42-46, 104-108, 385-386, 391-392, 399-400, 422-425, 455-456, 469-470
src/pages/ContractDetails.vue	98.33%	91.13%	100%	98.33%	74-78, 312

Generated in workflow #574

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
2 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication

The version of Java (11.0.17) you have used to run this analysis is deprecated and we will stop accepting it soon. Please update to at least Java 17.
Read more here

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[ericleponner]

LG