You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for developing such a useful snapshot testing library. I'm using it in a CycloneDX SBOM library. I received a dependabot PR to bump the version to the 1.18.0 version, but that had failing tests. When I investigated, I noticed that the JSON serialization output regressed, causing tests to fail. I assume it's related to the dependency changes and is likely caused by a bug in an upstream library, but I figured I should bring it to your attention, given its impact on the snapshot output.
The short description is that it seems like pretty-printed JSON is sometimes moved to the same line as the opening {, as shown in the snapshot output for the reproduction repository
What happened?
Thanks for developing such a useful snapshot testing library. I'm using it in a CycloneDX SBOM library. I received a dependabot PR to bump the version to the
1.18.0
version, but that had failing tests. When I investigated, I noticed that the JSON serialization output regressed, causing tests to fail. I assume it's related to the dependency changes and is likely caused by a bug in an upstream library, but I figured I should bring it to your attention, given its impact on the snapshot output.The short description is that it seems like pretty-printed JSON is sometimes moved to the same line as the opening
{
, as shown in the snapshot output for the reproduction repositoryReproduction steps
I created an example repository to demonstrate the issue. There is a PR open amy-keibler/example-insta-regression#1 with failing tests that demonstrate the issue in CI
insta
is~1.17.1
in themain
branchcargo test
and observe that they are passingdependency-upgrade
branchinsta
is1.18.0
cargo test
and observe that they are failing with the following outputInsta Version
1.18.0
rustc Version
No response
What did you expect?
No response
The text was updated successfully, but these errors were encountered: