chore(expect-type): update expect-type usage#7589
chore(expect-type): update expect-type usage#7589mmkal wants to merge 5 commits intovitest-dev:mainfrom
Conversation
✅ Deploy Preview for vitest-dev ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
I think new features should be documented in https://vitest.dev/api/expect-typeof.html |
|
@sheremet-va sounds good, will update that page soon, have set to draft in the meantime. Also is the breaking-change label because the method is deprecated? All existing |
|
Sorry I misunderstood the change. I thought that the old methods are going away because you updated the tests. It's fine to keep as a feature release |
mmkal
changed the title
|
I think this can be closed since #8397 added this information already |
2 participants
Description
Just getting ahead of renovate-bot and bumping expect-type because there are some downstream projects I'd like to get the new features in.
New features in expect-type:
.mapfn: .map fn mmkal/expect-type#98.toMatchObjectTypeand.toExtend: toMatchObjectType + toExtend - replacements for toMatchTypeOf mmkal/expect-type#126 - this deprecates.toMatchTypeOf(no plans to remove it any time soon though). I also updated the two usages of the deprecated method.Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
[ ][no issue, it's just a dependency update so hopefully fine?] It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.[ ][updated a test, but didn't see a need for a new one] Ideally, include a test that fails without this PR but passes with it.[ ][lockfile was updated, because it's a deps bump] Please, don't make changes topnpm-lock.yamlunless you introduce a new test example.Tests
pnpm test:ci. [some failures on my machine, but I think unrelated]Documentation
[ ]If you introduce new functionality, document it. You can run documentation withpnpm run docscommand.Changesets
feat:,fix:,perf:,docs:, orchore:.