microsoft / microsoft/AzureStorageExplorer
Persist column data independently for each blob container/file share/queue
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Column data for tables are preserved independently of each other. This is done primarily because tables have different columns.
Column data for blob containers, file shares, queues, etc. are preserved for all containers, shares, queues, etc. This is done primarily because they have the same set of columns.
However, it is likely that users may want to preserve different column data depending on the container. For example, auto-sized columns will differ from container to container depending on the data they contain (the Name column size will differ between containers). If preserved columns settings persist for all containers, an auto-sized column for one container would change the column size for all other containers, which would not be appropriate.
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 tracing how column data is currently preserved for tables, then compare that with the shared settings used by blob containers, file shares, and queues. Done means column settings, including auto-sized widths, are preserved independently for each container, share, or queue rather than affecting other resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100