Snapshot assertion APIs failed to work with not

[fenghan34]

Describe the bug

When I was trying to address #3089, I found that not only toThrowErrorMatchingInlineSnapshot() but also other snapshot assertion APIs like toMatchInlineSnapshot() do not seem to work with not.

Not sure if Vitest should support all of them, but at least a note in the documentation would be better.

Reproduction

https://stackblitz.com/edit/vitest-dev-vitest-bqujvz?file=test%2Fbasic.test.ts

System Info

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.14.0 - /usr/local/bin/pnpm
  npmPackages:
    @vitest/ui: latest => 0.29.7 
    vite: latest => 4.2.1 
    vitest: latest => 0.29.7

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sheremet-va]

As I said in #3089 (comment) I don't think we can support this. Snapshots are generated based on the input. If we use .not, then we cannot generate a snapshot because we don't know the input.

[fenghan34]

As I said in #3089 (comment) I don't think we can support this. Snapshots are generated based on the input. If we use .not, then we cannot generate a snapshot because we don't know the input.

Thanks for the reply, now I understand it. Maybe we can throw an error if users use these APIs with not, what do you think?

[sheremet-va]

Thanks for the reply, now I understand it. Maybe we can throw an error if users use these APIs with not, what do you think?

Sounds good to me 👍🏻

[sheremet-va]

Closed by #5294