Refactor to use ClientSchedule on client
Use the ClientSchedule data structure for deserialising and tracking edit state on the client instead of trying to directly deal with the ApiSchedule type which is not build for ease of edits or rendering.
This commit is contained in:
parent
ce9f758f84
commit
bb450fd583
15 changed files with 488 additions and 1297 deletions
|
@ -1,5 +1,5 @@
|
|||
// Wrapper around Luxon to make sure the throwOnInvalid option is set
|
||||
import { DateTime, FixedOffsetZone, Info, Settings, Zone } from "luxon";
|
||||
import { DateTime, Duration, FixedOffsetZone, Info, Settings, Zone } from "luxon";
|
||||
|
||||
Settings.throwOnInvalid = true;
|
||||
declare module 'luxon' {
|
||||
|
@ -8,4 +8,4 @@ declare module 'luxon' {
|
|||
}
|
||||
}
|
||||
|
||||
export { DateTime, FixedOffsetZone, Info, Zone }
|
||||
export { DateTime, Duration, FixedOffsetZone, Info, Zone }
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue