owltide/shared/utils/luxon.ts

/*
	SPDX-FileCopyrightText: © 2025 Hornwitser <code@hornwitser.no>
	SPDX-License-Identifier: AGPL-3.0-or-later
*/
// Wrapper around Luxon to make sure the throwOnInvalid option is set
import { DateTime, Duration, FixedOffsetZone, Info, Settings, Zone } from "luxon";

Settings.throwOnInvalid = true;
declare module 'luxon' {
	interface TSSettings {
		throwOnInvalid: true;
	}
}

export { DateTime, Duration, FixedOffsetZone, Info, Zone }
License under AGPL version 3 or later I firmly believe in free software. The application I'm making here have capabilities that I've not seen in any system. It presents itself as an opportunity to collaborate on a tool that serves the people rather than corporations. Whose incentives are to help people rather, not make the most money. And whose terms ensure that these freedoms and incentives cannot be taken back or subverted. I license this software under the AGPL. 2025-06-30 18:58:24 +02:00			`/*`
			`SPDX-FileCopyrightText: © 2025 Hornwitser <code@hornwitser.no>`
			`SPDX-License-Identifier: AGPL-3.0-or-later`
			`*/`
Implement ClientSchedule state tracking class Write the logic of keeping track of location modifications and applying updates from the server into the ClientSchedule class. This should serve as the foundation for replacing the prototype in-component update logic which have turned into an unmaintainable spagetti. 2025-06-12 21:45:34 +02:00			`// Wrapper around Luxon to make sure the throwOnInvalid option is set`
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. 2025-06-14 19:22:53 +02:00			`import { DateTime, Duration, FixedOffsetZone, Info, Settings, Zone } from "luxon";`
Implement ClientSchedule state tracking class Write the logic of keeping track of location modifications and applying updates from the server into the ClientSchedule class. This should serve as the foundation for replacing the prototype in-component update logic which have turned into an unmaintainable spagetti. 2025-06-12 21:45:34 +02:00
			`Settings.throwOnInvalid = true;`
			`declare module 'luxon' {`
			`interface TSSettings {`
			`throwOnInvalid: true;`
			`}`
			`}`

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. 2025-06-14 19:22:53 +02:00			`export { DateTime, Duration, FixedOffsetZone, Info, Zone }`