-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get Event Types parsing issue when running apps/api locally #10995
Comments
Thank you for opening your first issue, one of our team members will review it as soon as it possible. ❤️🎉 |
Seems like it could be something to do with the seeding of App Store trying everything in #6994... |
…on of apps/ai. Closes calcom#10995
Looks like we tracked it down. The issue was that in the package.json of our new app, we had a different zod version. This commit fixed it: RubricLab@31aa33f |
For anyone reading this in the future, make sure your package.json's have the right versioned deps (no conflicting versions) across the mono repo and make sure your node version is 18.x |
Found a bug? Please fill out the sections below. 👍
Issue Summary
It is very possible that I am missing something dumb and this Issue turns out to be embarrassing haha, sorry in advance if this wastes any time!
It seems as though calls to localhost:3002/api/event-types?apiKey=API_KEY are not working locally when standing up the monorepo.
Steps to Reproduce
yarn dev:api
Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
Actual Results
GET event-types
(/apps/api/pages/api/event-types/_get.ts) expects the following vars:But the parser schemaEventTypeReadPublic (apps/api/lib/validations/event-type.ts)
expects those to be type
never
Thus, we get an error at /api/event-types?apiKey=API_KEY
Expected Results
The parser should expect those vars OR explicitly removed OR stripped
Calls to /api/event-types?apiKey=API_KEY should return event types
Technical details
Evidence
Motivation
This bug was created because this PR can't be tested properly without a fix
The text was updated successfully, but these errors were encountered: