allow user to create new geojson layer, define active layer, drag&dro…

[digitaltom]

…p features between layers

[Copilot]

Copilot review overview

🔵 Needs a closer look

Unresolved moderate issues affect collaborative layer ordering, visibility controls, and layer-aware undo/redo.

Review effort: Lite
Findings: 3

Open (3)

• Undo/redo loses first-layer placement
• Preserve first-layer ordering across collaborative tabs
• Broadcast first-layer position to other clients

Resolved since last review (3)

• Restore the missing FileUtils require
• Escape user-controlled layer names in status messages
• Restrict layer lookup to GeoJSON layers

Previously missed (1)

In code that hasn't changed since last review

Preserve originating layer in feature undo state

app/​javascript/​maplibre/​layers/​layers.js:300

Feature undo states do not record their layer, while the new fallback here chooses the current active layer. If a feature is added or deleted in layer A, the user switches the active layer to B, and then undoes/redoes that operation, undo.js calls addFeature(state) and restores it in B; the server then infers B as well. Preserve the originating layer id in feature undo state and pass it to addFeature/new_feature so undo remains tied to the layer where the edit occurred.