Skip to content

Commit

Permalink
Refine changelog
Browse files Browse the repository at this point in the history
  • Loading branch information
max-sixty authored Oct 26, 2024
1 parent 0e07a50 commit 254abd8
Showing 1 changed file with 12 additions and 10 deletions.
22 changes: 12 additions & 10 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,16 +7,18 @@ All notable changes to insta and cargo-insta are documented here.
- Experimental support for binary snapshots. #610 (Florian Plattner)

- `--force-update-snapshots` now causes `cargo-insta` to write every snapshot, regardless of whether
it evaluates snapshots fully match, and now implies `--accept`. This
allows for `--force-update-snapshots` to update inline snapshots when
delimiters or indentation can be updated.

For the existing behavior of limiting writes to when `insta` evaluates writes
are required, use `--require-full-match`. The main difference between
`--require-full-match` and the existing behavior of `--force-update-snapshots`
is that `cargo-insta` will return a non-zero exit code if any snapshots don't
match fully. `--require-full-match` doesn't track inline snapshots' delimiters or
indentation. #644
snapshots fully match, and now implies `--accept`. This
allows for `--force-update-snapshots` to update inline snapshots'
delimiters and indentation.

For the previous behavior of `--force-update-snapshots`, which limited writes to
snapshots which didn't fully match, use `--require-full-match`.
The main difference between `--require-full-match` and the existing behavior of `--force-update-snapshots`
is a non-zero exit code on any snapshots which don't fully match.

Like the previous behavior or `--force-update-snapshots`, `--require-full-match`
doesn't track inline snapshots' delimiters or
indentation, so can't update if those don't match. #644

- Inline snapshots only use `#` characters as delimiters when required. #603

Expand Down

0 comments on commit 254abd8

Please sign in to comment.