Refactors calendar configuration and event handling
Streamlines calendar configuration by adopting a singleton pattern for consistent access and simplifies event handling.
- Removes direct `CalendarConfig` dependency injection in favor of the `calendarConfig` singleton, reducing code complexity.
- Replaces specific event emissions for grid, date, and resource settings updates with a general `REFRESH_REQUESTED` event.
- Updates event names to be more descriptive and consistent ("NAVIGATION_COMPLETED", "PERIOD_INFO_UPDATE").
- Removes the need to pass the calendar config to renderers since it is now a singleton.
This improves code maintainability and simplifies the event emission process.
This commit is contained in:
parent
d0936d1838
commit
2083c6921e
19 changed files with 139 additions and 173 deletions
|
|
@ -15,8 +15,8 @@ export const CoreEvents = {
|
|||
|
||||
// Navigation events (3)
|
||||
DATE_CHANGED: 'nav:date-changed',
|
||||
PERIOD_CHANGED: 'nav:period-changed',
|
||||
WEEK_CHANGED: 'nav:week-changed',
|
||||
NAVIGATION_COMPLETED: 'nav:navigation-completed',
|
||||
PERIOD_INFO_UPDATE: 'nav:period-info-update',
|
||||
|
||||
// Data events (4)
|
||||
DATA_LOADING: 'data:loading',
|
||||
|
|
@ -65,8 +65,8 @@ export const EVENT_MIGRATION_MAP: Record<string, string> = {
|
|||
|
||||
// Navigation
|
||||
'calendar:datechanged': CoreEvents.DATE_CHANGED,
|
||||
'calendar:periodchange': CoreEvents.PERIOD_CHANGED,
|
||||
'calendar:weekchanged': CoreEvents.WEEK_CHANGED,
|
||||
'calendar:navigationcompleted': CoreEvents.NAVIGATION_COMPLETED,
|
||||
'calendar:periodinfoUpdate': CoreEvents.PERIOD_INFO_UPDATE,
|
||||
|
||||
// Data
|
||||
'calendar:datafetchstart': CoreEvents.DATA_LOADING,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue