fix: use platformData.node/instance for correct guest grouping
The Dashboard grouping was broken because: - node was set to r.parentId (full resource ID) - instance was set to r.platformId Fixed to read from platformData which contains the correct values: - node = platformData.node (e.g., 'minipc') - instance = platformData.instance (e.g., 'https://pve:8006') This matches the legacy data format and fixes the grouped/list toggle.
This commit is contained in:
parent
ef135126b9
commit
f003ad7239
1 changed files with 4 additions and 4 deletions
|
|
@ -882,8 +882,8 @@ function App() {
|
||||||
id: r.id,
|
id: r.id,
|
||||||
vmid: platformData?.vmid as number ?? 0,
|
vmid: platformData?.vmid as number ?? 0,
|
||||||
name: r.name,
|
name: r.name,
|
||||||
node: r.parentId ?? '',
|
node: platformData?.node as string ?? '',
|
||||||
instance: r.platformId,
|
instance: platformData?.instance as string ?? r.platformId,
|
||||||
status: r.status === 'running' ? 'running' : 'stopped',
|
status: r.status === 'running' ? 'running' : 'stopped',
|
||||||
type: 'qemu',
|
type: 'qemu',
|
||||||
cpu: r.cpu?.current ?? 0,
|
cpu: r.cpu?.current ?? 0,
|
||||||
|
|
@ -926,8 +926,8 @@ function App() {
|
||||||
id: r.id,
|
id: r.id,
|
||||||
vmid: platformData?.vmid as number ?? 0,
|
vmid: platformData?.vmid as number ?? 0,
|
||||||
name: r.name,
|
name: r.name,
|
||||||
node: r.parentId ?? '',
|
node: platformData?.node as string ?? '',
|
||||||
instance: r.platformId,
|
instance: platformData?.instance as string ?? r.platformId,
|
||||||
status: r.status === 'running' ? 'running' : 'stopped',
|
status: r.status === 'running' ? 'running' : 'stopped',
|
||||||
type: 'lxc',
|
type: 'lxc',
|
||||||
cpu: r.cpu?.current ?? 0,
|
cpu: r.cpu?.current ?? 0,
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue