CRUD Type Errors on Compile or Restart
Hello! I am using wasps CRUD functionality but have run into an issue. To successfully compile and start, I have to copy and delete my CRUD declarations from main.wasp and then paste them back once it's compiled and started. Things then work normally until I need to restart again.
6 Replies
Hi @WulfCoDev. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
It sounds like you're experiencing an issue with CRUD declarations in your Wasp application during compilation and restart. This appears to be related to a known issue in Wasp where duplicate declaration names can cause problems during compilation.
Based on the knowledge sources, there's an open issue (#1234) that describes how the Wasp analyzer currently allows duplicate CRUD declarations with the same name, which causes the generator to fail with "duplicate file draft file names" errors during compilation:
Disallow duplicate declaration names
Your workaround of removing and re-adding the CRUD declarations is actually addressing this issue temporarily by avoiding the duplicate declarations during compilation.
There are a few things you can try:
1. Run
wasp clean followed by wasp start to get a fresh compilation. This might help resolve temporary issues as mentioned in several support threads:
- Make sure your CRUD declarations have unique names
- Check for any duplicate entity or operation names in your Wasp file
2. If you're making changes to configuration files or dependencies, you might need to restart the Wasp server completely as mentioned in another issue:
Tailwind config restart requirement
3. Check if there are any temporary files being created in your project directory that might be causing issues during compilation, as mentioned in issues #187 and #61.
This seems to be a bug in the current version of Wasp rather than something you're doing wrong. The team is aware of the issue with duplicate declarations and is working on a fix to properly validate declaration names during the analysis phase.
If you continue to experience issues, you might want to share your specific CRUD declarations in the Wasp Discord community for more targeted help.
I'm sorry you're experiencing this frustrating issue with the CRUD functionality!
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @WulfCoDev, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
relevant schemas to the CRUD declarations
@kapa.ai there are no duplicate names being used. When given the error messages from console, chatGPT says "This error is happening because UserWhereUniqueInput, UserCreateInput, and related types are not being properly serialized into SuperJSONValue. Wasp internally uses SuperJSON to handle complex objects for network communication, but certain Prisma-generated types are not inherently serializable."
Let me check the knowledge base for you again. One moment! :books:
----------------------
Based on the error message you're experiencing, it appears you're facing an issue with Prisma-generated types not being properly serialized by SuperJSON in Wasp. This is a different problem than what I initially thought about duplicate declarations.
Looking at the knowledge sources, there are several related issues that might help explain what's happening:
1. Prisma schema validation and handling issues are documented in an open GitHub issue Improve handling of invalid Prisma schemas, which mentions that sometimes fields aren't being recognized or compiled properly by Wasp depending on their position within entity objects.
2. There are also known issues with Prisma error handling in Wasp, as mentioned in several issues and Discord threads. For example, one issue notes that "if any DB ops fail we will throw a 500" instead of more descriptive error messages.
Some potential solutions to try:
1. Run
wasp clean and then wasp start again to get a fresh compilation, as mentioned in a Discord thread:
2. If you have no entities defined, you might need to define a dummy entity as a workaround:
Then run wasp db migrate-dev as mentioned in this GitHub issue.
3. Check if you have any optional relations in your entities that might be causing issues. As mentioned in a Discord thread, making certain relations optional (by adding a question mark) might help resolve Prisma-related errors.
4. Make sure you've run wasp db migrate-dev after any schema changes, as this is a common source of database-related errors.
The serialization issue with SuperJSON and Prisma types isn't explicitly mentioned in the knowledge sources, but it's likely related to how Wasp integrates with Prisma. If these solutions don't work, you might want to share your specific schema and error messages in the Wasp Discord community for more targeted help.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @WulfCoDev, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?@kapa.ai I changed two of my models using Decimal type to Float and the issue resolved itself
Hey @WulfCoDev, you've run into this issue: https://github.com/wasp-lang/wasp/issues/2503
And correctly concluded it has to do with the Decimal type. I've added this thread to the issue to help prioritize it
GitHub
Support Prisma's Decimal field in our serialisation · Issue #2503 ·...
Prisma has a Decimal type which SuperJSON can't handle, we need to implement custom handling for it. We should probably implement a custom serializer for the Prisma.Decimal type: https://github...