Merged
Conversation
… payload capacity columns - Vehicle migration: remove redundant capacity_weight_kg (use existing payload_capacity), rename capacity_volume_m3 → payload_capacity_volume, capacity_pallets → payload_capacity_pallets, capacity_parcels → payload_capacity_parcels to follow Fleetbase naming convention - Payload migration: remove all four redundant capacity columns (capacity_weight_kg, capacity_volume_m3, capacity_pallets, capacity_parcels) — these values are computed dynamically from payload entities, not stored as denormalised cache columns - Vehicle model: update fillable and casts to match renamed columns - Payload model: remove redundant capacity columns from fillable and casts - OrchestrationPayloadBuilder: read payload_capacity (existing column) for vehicle weight capacity; compute job amount array dynamically by aggregating entity weight/dimensions with unit normalisation — no longer reads stale payload capacity cache columns - VehicleController (Api/v1): add payload_capacity, payload_capacity_volume, payload_capacity_pallets, payload_capacity_parcels, skills, max_tasks, time_window_start, time_window_end, return_to_depot to create/update input whitelists - OrderController (Api/v1): add time_window_start, time_window_end, required_skills, orchestrator_priority to create/update input whitelists
…ns for capacity columns - Restore 2026_04_08_000001 and 2026_04_08_000004 to their exact released state; these migrations have already been run on live instances and must not be modified - Add 2026_04_14_000001: drop redundant payload capacity columns (capacity_weight_kg, capacity_volume_m3, capacity_pallets, capacity_parcels) which are now computed dynamically from entities by OrchestrationPayloadBuilder - Add 2026_04_14_000002: rename vehicle capacity columns to follow the payload_capacity_* naming convention and drop the redundant capacity_weight_kg (duplicate of the pre-existing payload_capacity column)
…s items Each item in every section array within createMenuPanels now carries an explicit `priority` integer, numbered from 0 (first) downwards in the order they appear in the source. This makes the sort deterministic and allows universe-registered extension items to interleave at any position by setting a matching priority value. Sections updated and their item counts: - operationsItems (5 items, priority 0–4) - resourcesItems (8 items, priority 0–7) - connectivityItems (4 items, priority 0–3) - maintenanceItems (5 items, priority 0–4) - analyticsItems (1 item, priority 0) - settingsItems (8 items, priority 0–7) The existing .sort((a, b) => (a.priority ?? 0) - (b.priority ?? 0)) on each array was already correct and is left unchanged.
All items injected from the universe registry into each section array are now mapped to include a `_virtual: true` flag before being spread into the array. This allows the sidebar template and any downstream consumers to distinguish between native FleetOps menu items and those registered by external extensions via the universe service. Sections updated: - universeOperationsMenuItems - universeManagementMenuItems - universeConnectivityMenuItems - universeMaintenanceMenuItems - universeAnalyticsMenuItems - universeSettingsMenuItems
…rm and details UI - vehicle/form.hbs: add Payload Volume (m³), Pallet Capacity, and Parcel Capacity inputs in the Capacity & Dimensions sub-section of Technical Specifications, alongside the existing payload_capacity (weight) field - vehicle/details.hbs: add Payload Volume, Pallet Capacity, and Parcel Capacity to the Orchestrator Constraints read-only panel; update the conditional guard to show the panel when any of the three new fields are set
…pdate help text - vehicle/form.hbs: update help text for payload_capacity_volume, payload_capacity_pallets, and payload_capacity_parcels to describe them as general vehicle specification fields rather than Orchestrator-specific fields - vehicle/details.hbs: move payload_capacity_volume, payload_capacity_pallets, and payload_capacity_parcels from the Orchestrator Constraints panel into the Capacity & Dimensions sub-section of Technical Specifications, consistent with where they appear in the form; restore Orchestrator Constraints guard to only skills/time_window/max_tasks
fix: correct orchestrator capacity column naming and remove redundant payload capacity columns
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.