microsoft / microsoft/AzureStorageExplorer
Table Entities (only upmost row) not shown in expected order.
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.6.2
Platform: Windows 10
When opening a table in Storage explorer I expect the rows sorted in the order of the contents of PartitionKey and RowKey.
Unexpectedly the upmost row does not follow this pattern. For example in a table in which all Entities have the same PartitionKey, the Entity with the lowest content should appear upmost. This is not the case. It can easily be handled by sorting the rows according to their RowKey but it is unexpected and in some way irritating.
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
Reproduce the ordering issue described for Azure Storage Explorer 1.6.2 on Windows 10 using a table with one PartitionKey and multiple RowKeys. Inspect how table entities are displayed and verify that the top row follows the expected PartitionKey and RowKey order; done means the lowest RowKey appears first when the PartitionKey values match.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100