Skip to content
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

Migrate type tests to Vitest #367

Merged
merged 43 commits into from
Jul 12, 2024

Conversation

aryaemami59
Copy link
Contributor

This PR:

  • Converts typetest.ts file extensions to test-d.ts to be compatible with Vitest.
  • Converts expectType() to either assertType() or expectTypeOf().toMatchTypeOf().
  • Converts expectExactType to expectTypeOf().toEqualTypeOf().
  • Converts lone-blocks to test or describe blocks.

Copy link

codesandbox-ci bot commented Feb 24, 2024

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@aryaemami59 aryaemami59 marked this pull request as ready for review February 24, 2024 13:31
@aryaemami59 aryaemami59 force-pushed the migrate-typetests-to-vitest branch 3 times, most recently from 038616e to 76e3cc6 Compare June 24, 2024 21:51
- It seems like the new version of Vite much like Node.js allows packages to self-reference themselves, which became a problem considering how we were running the tests against the build artifact during CI.
@aryaemami59
Copy link
Contributor Author

Had forgotten this still had some type tests that needed to be migrated to Vitest, all done now.

@timdorr
Copy link
Member

timdorr commented Jul 12, 2024

Looks great! Let's get it merged in.

@timdorr timdorr merged commit bf04cf7 into reduxjs:master Jul 12, 2024
20 checks passed
@aryaemami59
Copy link
Contributor Author

Thank you!!!!

@aryaemami59 aryaemami59 deleted the migrate-typetests-to-vitest branch July 12, 2024 23:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants