Refactor location actions
Description
With https://gitlab.hzdr.de/hub-terra/sms/backend/-/issues/117 we merge the begin and end locations. We want to make the required adjustments also in the frontend.
https://gitlab.hzdr.de/hub-terra/sms/backend/-/issues/118 can also be helpful for that.
Useful Hints
- Dynamic Begin Location Form to load the device properties for the active devices to select the x,y,z properties:
-
/configurations/<config_id>/device-mount-actions?include=device,device.device_properties
- Filtering for the appropriate date
- current version:
Todos/Acceptance
- current behavior of the location section should be mirrored
- landing page
/locations
- has date picker
- has Select List
- displays all location actions of the configuration
- e.g.:
2022-07-28 05:19 - Dynamic location begin
- e.g.:
- has also an item
now
to select current time- e.g.:
2022-08-17 10:08 - Now
- e.g.:
- has also an item
selected
to select current time- e.g.:
2022-08-17 10:07 - Selected
- if you select an item of the list, the date of the date picker updates
- if you select a date via date picker, the select list updates:
- if there is an action with the same date, that item will be displayed
- otherwise:
selected
with the corresponding date is displayed
- e.g.:
- displays all location actions of the configuration
- has Buttons
Start Static Location
andStart Dynamic Location
- leading to the corresponding forms to create a new begin location action
- are only visible if no actions is currently displayed
- if an action is selected via select list
- a card with the corresponding information are displayed
- if a begin action is selected
- if it has a end action, both information will be displayed
- if an end action is selected
- the corresponding start action will be displayed
- if a begin action is selected
- a three dot menu, with delete and edit (if the actions has no end action)
- an action button with
STOP STATIC LOCATION
orSTOP DYNAMIC LOCATION
if the action has not end action, otherwiseEDIT
- leading to the corresponding forms to create a new end location action
- a card with the corresponding information are displayed
- first line of forms are the disabled date picker and select list of landing page
- UI Changes compared to old version:
- timepoint should not be a part of the route:
- ids should be used
- fallback, if the ids doesn't work: timepoint as a route parameter
- landing page
Edited by Tobias Kuhnert