microsoft / microsoft/AzureStorageExplorer
Keep a consistent Content Type value for one ADLS Gen2 folder between Editor and Properties dialog
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Storage Explorer Version: 1.13.0
Build: 20200422.4
Branch: rel/1.13.0
Platform/OS: Windows 10/ Linux Ubuntu 18.04/macOS High Sierra
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:
- Expand one ADLS Gen2 storage account -> Blob Containers.
- Create a blob container -> Upload one folder.
- Right click the folder -> Click 'Properties...'.
- Check the Content type on properties dialog.
Expect Experience:
Display a consistent Content Type value between Editor and Properties dialog.
Actual Experience:
- Display an inconsistent Content Type value between Editor and Properties dialog.
- The ContentType value is null in Properties dialog.

- Open the Properties dialog -> Click 'Save' -> Re-open the Properties dialog.
The ContentType value is changed to 'application/octet-stream'.

More Info:
For one new created ADLS Gen2 folder
- The ContentType value is 'application/json; charset=utf-8'.

- Open the Properties dialog -> Delete the current ContentType value -> Click Save -> Re-open the Properties dialog. The ContentType value is changed to 'application/octet-stream'.

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 by reproducing the issue with an ADLS Gen2 folder and compare the Content Type shown in the Editor and Properties dialog. Trace how the Properties dialog reads and saves ContentType, then verify that reopening it preserves the same value without changing it to null or application/octet-stream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100