Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds snapshot testing to the repo using Verify
As an initial example i added a test for the API. This means any time the public API changes you need to accept that change. this secondary (in addition to the code that changes the api) acceptance serves as a confirmation of any change and the api change to be visualized in different way
to accept any change there are a variety of approaches https://github.com/VerifyTests/Verify?tab=readme-ov-file#snapshot-management
if u want to see the workflow for managing snapshots:
if u want to see some more content on how verify works https://github.com/VerifyTests/Verify?tab=readme-ov-file#media
let me know if u want to jump on a call to discuss any of the above