Open
Conversation
Turns out you can't import Prisma client side, so this fixes that by exporting a vetted and build time checked version of the TimeSlot field. This could be done programatically with a hook/generate script of some kind, but I don't know how those work.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🧩 Summary
Fixes the issues had in #1077.
🔗 Related issues (if any)
Closes nothing because we never made an issue
📸 Screenshots / recordings (if applicable)
before: 500 server error page (was gone in production because of hotfix)
now: successfully renders webpage
💬 Other information
There is a way to generate the typing of the enum programatically with a prisma generate script / macro or something similar, but afaik that's not something we've done previously, and frankly I was dissuaded because it seemed complicated. This was a good solution to me.