🐛[BUG] ProTable ColumnsSetting 将某一列固定到左或者右，排序order值不会同步更新

[linco-lin]

提问前先看看：

https://github.com/ryanhanwu/How-To-Ask-Questions-The-Smart-Way/blob/main/README-zh_CN.md

🐛 bug 1 描述

ProTable ColumnsSetting 选择固定列到左或者右，不会触发排序 order 值的更新

📷 复现步骤

步骤1：当前Column3的order是2，没有固定到左边：
{
"Column1": {
"show": true,
"fixed": "left",
"disable": true,
"order": 0,
},
"Column2": {
"show": true,
"order": 1,

},
"Column3": {
"show": true,
"order": 2,
}
}
步骤2：将Column3到固定到左边， 实际排序变了，但是order值没有更新，依旧是2：
{
"Column1": {
"show": true,
"fixed": "left",
"disable": true,
"order": 0,
},
"Column3": {
"show": true,
"fixed": "left",
"order": 2,
},
"Column2": {
"show": true,
"order": 1
}
}

🏞 期望结果

order 应该根据UI显示的顺序同步更新如下：
{
"Column1": {
"show": true,
"fixed": "left",
"disable": true,
"order": 0,
},
"Column3": {
"show": true,
"fixed": "left",
"order": 1,
},
"Column2": {
"show": true,
"order": 2,

}
}

💻 复现代码

© 版本信息

• ProComponents 版本: [2.8.3]
• umi 版本
• 浏览器环境
• 开发环境 windows

🚑 其他信息

[dosubot]

This is a confirmed bug, and there's actually an earlier report of the same issue in #9287 [1].

Root cause: The ToolTipIcon pin/fix click handler only updates the fixed field in columnsMap and never recalculates order or updates sortKeyColumns [2]:

onClick={(e) => {
  const config = columnsMap?.[columnKey] || {};
  const columnKeyMap = {
    ...columnsMap,
    [columnKey]: { ...config, fixed } as ColumnsState,  // only sets `fixed`
  };
  setColumnsMap(columnKeyMap);  // `order` is NOT recalculated
}}

By contrast, the drag-and-drop move function correctly reassigns sequential order values for all columns after repositioning [3]:

newColumns.forEach((key, order) => {
  newMap[key] = { ...(newMap[key] || {}), order };
});
setColumnsMap(newMap);
setSortKeyColumns(newColumns);

To fix this, the ToolTipIcon onClick handler should, after updating fixed, also reconstruct the sorted column order (using the same logic as columnSort [4]) and reassign sequential order values — mirroring what the move function already does for drag-and-drop. As of now, no merged fix has been found for this issue.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.