#731 Projection Tab Autocomplete, Case Insensitive Mission Sorting, S…

[tariqksoliman]

…mart field dsiabling in /configure

Closes #731

With GPT-5

PR summary

• Projection auto-populate for Coordinates tab

  • Added a new action/button to tab-coordinates-config.json: “Auto-Populate Projection Fields From tilemapresource.xml or ArcGIS MapServer”.
  • Implemented handler in Maker.js:
    • Parses local/relative tilemapresource.xml (BoundingBox, Origin, TileSet order/units-per-pixel).
    • Parses ArcGIS MapServer ?f=pjson for fullExtent/initialExtent, tileInfo.origin, tileInfo.lods (prefers level 0) ArcGIS MapServer pjson.
    • Updates: projection.bounds, projection.origin, projection.reszoomlevel, projection.resunitsperpixel.
    • Shows success/error snackbars.

• Make “Custom Projection” state obvious in UI (disable while off)

  • Introduced a generic disableSwitch meta key for any component in metaconfigs:
    • If set (e.g., "disableSwitch": "projection.custom"), the component is disabled and greyed out unless the referenced boolean is true.
  • Applied to these Coordinates tab fields and button:
    • projection.epsg, projection.proj, projection.bounds.[0-3], projection.origin.[0-1], projection.reszoomlevel, projection.resunitsperpixel, projection.xmlpath, and the projection-populate-from-x button.
  • Renderer behavior:
    • Honors the current config value of the referenced switch.
    • If unset, falls back to the switch’s defaultChecked in the same row (fixes cases like coordinates.coordll).

• Case-insensitive mission sorting (Configure + Landing)

  • Frontend:
    • configure/src/core/Configure.js: Sort missions via localeCompare(..., { sensitivity: 'base' }) before storing.
    • src/App.js: Sort missions case-insensitively before passing to LandingPage.init.
    • configure/src/pages/Users/Modals/UpdateUserModal/UpdateUserModal.js: Sort available missions in the multiselect.
  • Backend:
    • API/Backend/Config/routes/configs.js: Returns missions sorted case-insensitively.

Files changed (high-level)

• configure/src/core/Maker.js: New projectionPopulateFromX, button action wiring, generic disableSwitch support across component types, fallback to defaultChecked.
• configure/src/metaconfigs/tab-coordinates-config.json: New button for auto-populate; disableSwitch on all projection inputs and action; minor copy update for xmlpath.
• configure/src/core/Configure.js, src/App.js, configure/src/pages/Users/Modals/UpdateUserModal/UpdateUserModal.js: Case-insensitive sorting on missions.
• API/Backend/Config/routes/configs.js: Case-insensitive sorting on missions response.

How to test

• Configure → Coordinates:
  • With projection.custom OFF, verify all projection fields and the auto-populate button are disabled.
  • Toggle ON; verify fields/buttons enable.
  • Enter a valid tilemapresource.xml path and click auto-populate → fields fill and success snackbar appears.
  • Enter a valid ArcGIS MapServer URL with ?f=pjson and click auto-populate → fields fill as above.
• Configure sidebar:
  • Missions list appears A–Z regardless of case.
• Landing page:
  • Missions appear A–Z regardless of case.
• Users → Update User modal:
  • Assigned Missions multiselect options appear A–Z regardless of case.

Compatibility and docs

• Backward compatible. disableSwitch is optional and non-breaking.
• Consider adding a brief note to the metaconfig authoring docs about the new "disableSwitch": "<boolean field path>" behavior.

Security/other

• Only reads local mission-relative XML when provided; ArcGIS JSON fetched from explicit URL. No new write endpoints added.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.7% Duplication on New Code

See analysis details on SonarQube Cloud