microsoft / microsoft/AzureStorageExplorer
Add option or toggle to show Blob properties' ContentMD5 in hex (Base16) instead of Base64
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Preflight Checklist
- I have installed the latest version of Storage Explorer.
- I have checked existing resources, including the troubleshooting guide and the release notes.
- I have searched for similar issues.
Problem
All of my tooling works with content hashes, like MD5, uses hexadecimal (Base16 ) representations, not Base64, so whenever I copy a blob's ContentMD5 value from Azure Storage Explorer I need to convert it from Base64 to Base16 which disrupts my workflow.
Examples of tooling that requires Base16, not Base64:
- SQL Server Management Studio's Grid View shows
varbinaryvalues in hexadecimal with an0xprefix - 7-Zip's hash tool (an Explorer.exe shell-extension) shows all hashes in Base16
- Excel doesn't support Base64, but it does support Base16 (
=HEX2DECand=DEC2HEX)
Desired Solution
A toggle button within the ContentMD5 textbox that flips the display between Base16 and Base64, and the last-used-setting is persisted
Alternatives and Workarounds
No response
Additional Context
If this feature is implemented, I'm not bothered either-way if the box has a leading 0x or not.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Blob properties ContentMD5 textbox described in the issue and trace how its displayed value and settings are handled. Add a Base16/Base64 toggle with persistence for the last-used choice, and verify that the ContentMD5 value displays in the selected format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100