Description
Snapshots in different realm folders can legitimately share a file name. The most common case is the shared auto snapshot, which is always named LastPublished-<manifestId>.json in every realm folder, so any workspace that has published to two or more realms has several snapshots named LastPublished-global. Manually created snapshots can also reuse a name across realms.
#4743 fixed the Snapshot tab hanging on these duplicates (fix: #4744), but once that fix lands, the tab lists same-named snapshots as visually identical rows. The list shows only the snapshot name; the realm is visible only after selecting a row, in the detail pane's "Realm" field.
Expected
Rows in the Snapshot tab list that share a name should be distinguishable at a glance - for example by showing the realm name or PID next to the snapshot name (either always, or only when a name appears more than once in the list).
Actual
Two LastPublished-global entries from different realms render as identical rows in the list. The only way to tell them apart is to select each one and read the Realm field in the detail pane. Users currently work around this by renaming the snapshot file to embed the PID, which defeats the stable auto-snapshot file name.
Notes
Description
Snapshots in different realm folders can legitimately share a file name. The most common case is the shared auto snapshot, which is always named
LastPublished-<manifestId>.jsonin every realm folder, so any workspace that has published to two or more realms has several snapshots namedLastPublished-global. Manually created snapshots can also reuse a name across realms.#4743 fixed the Snapshot tab hanging on these duplicates (fix: #4744), but once that fix lands, the tab lists same-named snapshots as visually identical rows. The list shows only the snapshot name; the realm is visible only after selecting a row, in the detail pane's "Realm" field.
Expected
Rows in the Snapshot tab list that share a name should be distinguishable at a glance - for example by showing the realm name or PID next to the snapshot name (either always, or only when a name appears more than once in the list).
Actual
Two
LastPublished-globalentries from different realms render as identical rows in the list. The only way to tell them apart is to select each one and read the Realm field in the detail pane. Users currently work around this by renaming the snapshot file to embed the PID, which defeats the stable auto-snapshot file name.Notes
ProjectData.RealmName/ProjectData.PID), so this is a display-layer change only; no file naming changes are needed or wanted (see the discussion of why encoding the realm into the file name is undesirable in Content window Snapshot tab hangs at 'Loading snapshots' when snapshots in different realms share a name #4743).