feat: create prefer-snapshot-hint
rule
#1012
Merged
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.
hint
instead ofname
as that's what the argument is called in the docs - however the docs do refer to it in a few places as "snapshot name" and it is used as part of the name. @SimenB imo it would be good to be consistent, so would be good if you could weigh in on if you'd preferhint
orname
and I can do the legwork of making a PR tojest
updating the docs and argument(s) to matchnever
option because I really don't think that is something people should be doing since there's no gain in not having a hint.multi
as the default because I think that is reasonable to assume the test title has enough context for one external snapshot matcher, but as soon as you have multiple in a single test you can't tell what each snapshot actually is from the snap along without a hint.Resolves #103