mirror of
https://github.com/Sendouc/sendou.ink.git
synced 2026-07-16 17:00:02 -05:00
09851faf83
* Issue 858: On the new calendar page adding a new Date entry with the "Add" button will now insert a new date with an offset of +24 hours of the previous row's date value. * Added comment to ignore the TSLint "object can be null" error * Changed `var` to `const` * Fixed Prettier checks in CI pipeline * Fixed Typecheck CI pipeline error * Moved getDateWithHoursOffset() function to app/utils/dates.ts * Added new line at end of file * Added getValidNewDateIfInvalid() function. This retrieves a valid date. If invalid, get a new Date object. - So now, if we intentionally/accidentally delete the data in the Calendar's DateInput element, it will be reset to the current Date/Time * Refactored DateInput component's update state mechanism to be handled by an onChange() function defined in the parent component that is passed to the child * Prettier formatting so that the new CI pipeline won't output errors at me * Removed unused imported types * Removed the datesCount React Hook & refactored accordingly * Removed unused loader-related variables * DateInput onChange prop is now optional * Instead of generating a new Array, iterate over DateInput's inputState's array instead * Fix potential undefined error * DatesInputState: refactored to remove index & access the index during iteration with map() 2nd arg * Properly initialized state for pre-existing events =) - Also added TODO comments for improving date input handling (1082) * Prettier formatting * Uncommented console.warn() * Touched up comment |
||
|---|---|---|
| .. | ||
| arrays.ts | ||
| dates.ts | ||
| fetch.ts | ||
| i18n.server.ts | ||
| i18next.ts | ||
| images.ts | ||
| number.ts | ||
| remix.ts | ||
| sql.ts | ||
| strings.ts | ||
| types.ts | ||
| unslugify.server.ts | ||
| urls.ts | ||
| zod.ts | ||