You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After following the docs and migrating the code, I have noticed that high CPU usage while coding and the auto-completion service was getting stuck on loading state.
Does this problem still occur when you restart your computer? Are you sure it did not happen with the previous version? Can you double check? I do not think this is related to our source code.
Yes, you are right. The odd part is, I was a bit sure that I got this issue after the upgrade but seems like I got the timeline wrong 😓 I have downgraded the versions on the minimal repo, and it is still reproducible.
If I comment out the return line in this function, there's no CPU issue. But when I return scope from the function, then the TS Server goes crazy.
After converting the function as the same in the type definition file, problem gone. However, if I don't specify the return type manually, it still causes TS server issue, strange.
The main point of doing this is to create a reusable facilitator function that creates a form but with a bit of sugar to trigger the validate function when the lang/language gets a reactive update.
Since the above version solves the issue, I guess it is safe to close the issue.
Thank you for leading it to double-check @fabian-hiller 🙏🏻
After following the docs and migrating the code, I have noticed that high CPU usage while coding and the auto-completion service was getting stuck on loading state.
Repro case: https://github.com/seahindeniz/valibot-issue
Steps:
pnpm create solid
pnpm create vite valibot-test --template vanilla
valibotUtils.ts
and try to type something likev.Gen
Record:
980d1c54-2022-478b-b00d-ce20a4c0f2f8.mp4
The text was updated successfully, but these errors were encountered: