ref(tests): Add instasnapshot types to various tests#108280
Merged
lobsterkatie merged 1 commit intoFeb 23, 2026
Merged
Conversation
github-actions
Bot
added
the
Scope: Backend
lobsterkatie
force-pushed
the
kmclb-add-instasnapshot-types-to-various-tests
branch
from
c2a7a19 to
17e5f38
Compare
lobsterkatie
deleted the
kmclb-add-instasnapshot-types-to-various-tests
branch
mchen-sentry
pushed a commit
that referenced
this pull request
Feb 24, 2026
This adds types to functions in tests where we're using the instasnapshotter. It's not meant as comprehensive typing for those files; rather, it came up while I was cleaning up snapshots in the wake of #103243 (which simplified snapshot headers in an effort to avoid merge conflicts).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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 types to functions in tests where we're using the instasnapshotter. It's not meant as comprehensive typing for those files; rather, it came up while I was cleaning up snapshots in the wake of #103243 (which simplified snapshot headers in an effort to avoid merge conflicts).