chore: suppress error/warning spam in unit tests (v2.1.2)#642
Open
chore: suppress error/warning spam in unit tests (v2.1.2)#642
Conversation
Contributor
|
Current unit coverage is 88.86606409202957% |
anguyen-yext2
approved these changes
Mar 3, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Main purpose of this change is to clean up a lot of the log spam that was showing during unit test checks. The warnings/errors were not actionable and did not indicate an actual issue, so they were muted.
Additionally, added some listener cleanup to the
SearchI18nextProvideras well as language fallback (was the cause of some of the warnings).J=WAT-4717
TEST=auto