-
Notifications
You must be signed in to change notification settings - Fork 2
Update to TS 5 #1875
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
base: main
Are you sure you want to change the base?
Update to TS 5 #1875
Conversation
… of update to TS5
| set( | ||
| produce((state: QueuedTasksStore) => { | ||
| state.publications[val] = null; | ||
| state.publications[val] = { response: null }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes me a little nervous but i can't find anywhere that the publications object is even used - is this vestigial?
also removed obsolete @typescript-eslint/no-implicit-any-catch disable comments and changed catch clause types from `any` to `unknown`.
suppressImplicitAnyIndexErrors flag and address errors| "types": ["vite/client"] | ||
| }, | ||
| "include": ["src", "deps/flow/flow.d.ts", "deps/supabase/types.d.ts"], | ||
| "include": ["src", "deps/flow/flow.d.ts", "deps/supabase/types.d.ts", "__mocks__/vitest-env.d.ts"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'm new to vitest - is this a safe change to make?
Issues
https://github.com/estuary/ui/issues/issue_number
Changes
issue_number
Tests
Manually tested
Automated tests
Playwright tests ran locally
Screenshots
If applicable - please include some screenshots of the new UI