* WIP, WIP, WIP, WIP
* Adds missing types
* Type fixes for useSlots
* Type fixes
* Fixes periodType 500 error when updating
* Adds missing dayjs plugin and type fixes
* An attempt was made to fix tests
* Save work in progress
* Added UTC overflow to days
* Update lib/availability.ts
Co-authored-by: Alex Johansson <alexander@n1s.se>
* No more magic numbers
* Fixed slots.test & added getWorkingHours.test
* Tests pass, simpler logic, profit?
* Timezone shifting!
* Forgot to unskip tests
* Updated the user page
* Added American seed user, some fixes
* tmp fix so to continue testing availability
* Removed timeZone parameter, fix defaultValue auto-scroll
Co-authored-by: Omar López <zomars@me.com>
Co-authored-by: Alex Johansson <alexander@n1s.se>
* Fixed#1015 - Teams user registration is broken
* Type fixes for avilability form in onboarding
* Re adds missing strings
* Updates user availability in one query
Tested and working correctly
* Fixes seeder and tests
Co-authored-by: Omar López <zomars@me.com>
* Refactored Schedule component
* Merge branch 'main' into feature/availability-page-revamp
* wip
* Turned value into number, many other TS tweaks
* NodeJS 16x works 100% on my local, but out of scope for this already massive PR
* Fixed TS errors in viewer.tsx and schedule/index.ts
* Reverted next.config.js
* Fixed minor remnant from moving types to @lib/types
* schema comment
* some changes to form handling
* add comments
* Turned ConfigType into number; which seems to be the value preferred by tRPC
* Fixed localized time display during onboarding
* Update components/ui/form/Schedule.tsx
Co-authored-by: Alex Johansson <alexander@n1s.se>
* Added showToast to indicate save success
* Converted number to Date, and also always establish time based on current date
* prevent height flickering of availability
by removing mb-2 of input field
* availabilty: re-added mb-2 but added min-height
* Quite a few bugs discovered, but this seems functional
Co-authored-by: KATT <alexander@n1s.se>
Co-authored-by: Bailey Pumfleet <pumfleet@hey.com>
Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
Co-authored-by: Peer Richelsen <peeroke@gmail.com>
Previously, when creating a new event type, user was still allowed to create a new event type, even if the event length's field was empty. This would cause a prisma error, since it would receive NaN and no event would have been added, but the page still reloaded. Therefore, a very basic validation to address this, at least in the short-term.
Syed Ali Shahbaz