Feat: Split recurrence and events into separate pages#16
Open
AlexianMasson wants to merge 7 commits into
Open
Conversation
AlexianMasson
changed the title
georchestra/database:26.0.0 bundles 120-datafeeder.sql with the same schema, so running 130-datafeeder.sql after it fails with "type rule_type_enum already exists". Pin the base image tag to stop silent breakage on future upstream changes. The script is kept at docker/datafeeder-init.sql for installations on an existing database that don't use the georchestra base image.
Add isRemoteDataset to the store and insert a 'recurrence' route between edit and authorizations in accessibleRoutes (remote, owner/admin only). Events is dropped from the linear next/prev chain.
New RecurrenceComponent rendering only the interval dropdown, reachable at /:id/recurrence and guarded by rejectNonRemoteDatasetGuard (redirects non-remote datasets back to /edit).
Move the recurrence selector and schedule logic out of EventsComponent; the page now shows only the events list and is titled 'Événements'.
Side panel order is now Métadonnée, Récurrence, Droits, Événements, separator, Dashboard. Récurrence is greyed for non-remote datasets (local and empty tooltips). The layout footer is registered only for the recurrence/authorizations flow pages, so the events page has no footer.
Add sidebar.recurrence, sidebar.unavailableForLocal, footer.next.recurrence and footer.saveAndNext.recurrence; retitle the events labels to 'Événements'.
AlexianMasson
force-pushed
the
feat/split-recurrence-events-pages
branch
from
9159b81 to
74bac16
Compare
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.
Based on #15
The recurrence section has been extracted out of the events page into its own standalone route and component.