23 Replies
Can I see your tsconfig?
In this case the type error is correct, there are a lot of columns in your table marked as
not null
without defaultbut update set doesn't require every column to be modified
If you are inserting, you need to provide all non null columns that doesn't have a default
I sent the wrong screenshot here by accident.
Yes, I just talking about this case
Oh, ok
Let me see the other one
This one I sent earlier: https://discord.com/channels/1043890932593987624/1043890932593987627/1193574212569419797
I can't reproduce. It works totally fine for me
Could be WebStorms fault then.
Your tsconfig seems fine too
I'll try with some other IDE tomorrow
I don't even know what WebStorms is lol
I thought it was a framework
It's Jetbrains proprietary javascript IDE
I like it for the great tooling.
Can you reproduce the error in vscode?
They did write in a blog post recently that they have their own language server implementation and wanna have a hybrid system with the official typescript language server in the future.
Ooff
The JetBrains Blog
Try the Future TypeScript Engine With the WebStorm@next Program | T...
There is an experimental WebStorm@next build, which introduces improved type inference for enhanced performance and accuracy. You can install it via the Toolbox App.
Why reinvent the wheel
Personally I heard the typescript language server likes to be slow and crash a lot. I think they also have it because it allows them to better integrate with their own completion systems.
That's what I'll do tomorrow.
Seems reasonable
I think my lsp is tsserver
It didn't show me an error
Seems like WebStorm supported typescript before they even had a official language API https://blog.jetbrains.com/webstorm/2024/01/everything-you-ve-always-wanted-to-know-about-typescript-s-integration-in-webstorm/
The JetBrains Blog
Everything You’ve Always Wanted to Know About TypeScript’s Integrat...
WebStorm's TypeScript integration evolved from a basic compiler to an advanced service, adapting to TypeScript's changes, especially the challenging shift to TypeScript 5.