microsoft / microsoft/AzureStorageExplorer

Template for table storage column arrangement

Open
#8,304 1 comment 0 reactions 0 assignees View on GitHub

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
Problem

The default column order is not desirable

Desired Solution

I have thousands of tables that have largely the same properties. I would like to specify a template for the default column order. My initial thought is a text field where I can enter a list of entity properties separated by commas/semicolons in the order I would like the columns to appear. If a column name/property is not in that list, it uses the normal alphabetical sort order.

Alternatives and Workarounds

No response

Additional Context

For example, I have numerous tables that have entities with these properties: alarmDateStart; alarmDateStatus; alarmStatus; ID; Name; TagID; tagAlarmHint; tagName. I really want to see the tagName property first. I can drag and drop or rearrange the table columns, but doing that for every table is a burden. I want Storage Explorer to have a textbox where I could enter the string "tagName; tagAlarmHint; Name; alarmStatus; alarmDateStart; alarmDateStatus", and then when it loads a batch of table entities, it checks that list. If a property is in the list, it appears in the order of that list. The remaining properties are default ordered.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at Storage Explorer's table entity view and the existing drag-and-drop column arrangement described in the issue. Trace how table entity properties are collected and how column order is retained, then determine where the proposed template text field belongs. Done means a saved property order is applied across tables, with unspecified properties using the default ordering.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
desktop, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.