[MaxNumerique]

No description provided.

[MaxNumerique]

CRS support — shared front part

Part of the CRS work for Geode-solutions/Vease#798. Overview of the 4 PRs and merge order: see Geode-solutions/Vease#818. Merge after Geode-solutions/OpenGeodeWeb-Back#286: the front calls the new crs/* routes, and the old geographic_coordinate_systems route is removed.

Design rule: the shared components only display the CRS and request an edit. The dialog lives in the host app (Vease), which opts in with enableCrsEdit(). Apps that do not opt in show the CRS without edit buttons.

New

• stores/crs.ts — useCrsStore
  • geographicList(geodeObjectType): session cache of the CRS list (~13k entries), one Map entry per type holding the promise, so concurrent calls share one request. A failed or rejected request is removed from the cache so the next call retries.
  • crsEditEnabled / enableCrsEdit(): the host app says it can edit a CRS.
  • crsEditRequest / requestCrsEdit(id) / clearCrsEditRequest(): edit request channel.
• utils/crs.ts: formatCrs(crs) → EPSG:2154 — RGF93 v1 / Lambert-93 or None; formatCrsCode(crs) → EPSG:2154 or None.
• composables/live_data_item.ts — useLiveDataItem(id): live Dexie view of a data item whose id can change (virtual tree rows are reused; the info card follows the last object). One effect scope per id, stopped on id change and unmount.

Changed

• stores/data.ts: crs?: CRSList on DataItem / NewDataItem, copied in addItem. It survives project save/load (exportStores / import). Not indexed, so no Dexie version bump.
• ItemLabel.vue (+ show-crs in GlobalObjects.vue only): tooltip line CRS: <formatCrs> and an editCrsBtn when edit is enabled. The stored item is only read while the tooltip is open (v-tooltip v-model), so a long tree does not keep one live query per row.
• InfoCard.vue: CRS badge for data (not model components), code only with the full name in a tooltip, infoEditCrsBtn as a v-btn (keyboard accessible). Reads the item live, falls back to metaData.crs.
• CrsSelector.vue:
  • list from useCrsStore().geographicList (cached), held in a shallowRef;
  • row key authority:code (codes are only unique within an authority, e.g. EPSG:4812 vs ESRI:4812);
  • new compact prop for narrow panels: 2 columns (EPSG:2154, then the name truncated with an ellipsis and a tooltip), all with Vuetify header options (nowrap, width, maxWidth), search icon inside the field;
  • page sizes 10/25/50/100: no "All" (it would render every CRS at once);
  • API change: keyToUpdate prop and the stepper emits (update_values, increment_step) are removed. No consumer used them in the workspace; no BREAKING CHANGE footer since there is no compatibility to keep yet.
• Feedback — stores/feedback.ts, FeedBack/Snackers.vue: add_success(description, action?) / add_warning(description, action?) with FeedbackAction = { label, onClick } (exported). The snackbar shows a pencil button (feedbackActionBtn, tooltip = label); a click runs the action, then closes the snackbar, even if the action throws. The close button gets feedbackCloseBtn. Existing calls are unchanged.
• utils/import_workflow.ts: reloadObject(id, { rebuildActor = false }) extracted from applyTimeSeriesWorkflow. rebuildActor: true (convert/align) rebuilds the local actor from the new light viewable; time series keep the previous behavior (actor kept).
• internal/stores/hybrid_viewer/scene.ts — addItem: when an actor is replaced, the camera is no longer reset; new actors get the current z-scale (setScale(1, 1, zScale)).

Tests

stores/crs (shared request, failures not cached, edit requests), utils/crs, stores/data (crs copied, save/load), stores/feedback (action stored or absent), Snackers (no button without action, action then close, failing action still closes), ItemLabel (CRS row, edit button, virtual list reuse, no read while closed), InfoCard (CRS, button is a <button>, no row for model components, live value), CrsSelector (store, authority collision, compact columns, no "All"), import_workflow (rebuildActor on/off, time series).

Known limitations

• FeedbackAction always shows a pencil icon and add_error takes no action: enough for the CRS use, to extend if another use comes.