microsoft / microsoft/AzureStorageExplorer

Column order is not preserved after dragging columns then loading more entities that add new columns

Open
#5,952 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:gear: tables
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

When loading more entities in a large table, sometimes the new entities add new columns to the data table. However, if the existing columns have been reordered via drag and drop (not using the Custome Columns dialog), the previous column order is lost.

Repro Steps

  1. Create a CSV file using the following Node script:
    const fs = require("fs");
    const head = "PartitionKey,RowKey,V1,V1@type,V2,V2@type,V3,V3@type";
    let out1 = "";
    let out2 = "";
    let out3 = "";
    for (let i = 0; i < 1001; i++) {
        out1 += `\n,1_${i.toString().padStart(4, "0")},true,Boolean,,,,`;
        out2 += `\n,2_${i.toString().padStart(4, "0")},,,true,Boolean,,`;
        out3 += `\n,3_${i.toString().padStart(4, "0")},,,,,true,Boolean`;
    }
    fs.writeFile("coltest.csv", head + out1 + out2 + out3, () => { });
    
  2. Create a new table.
  3. Import the CSV file (this may take a minute or two).
  4. Reorder one of the columns by dragging and dropping the column header.
  5. Click Load More at the bottom of the table.

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

Use the provided Node.js script to generate coltest.csv, import it into a new table, reorder a column by dragging, and click Load More. Trace how the table retains column order while new entity columns are added. Done means the dragged order remains unchanged and the new columns are incorporated correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.