revert: Improve HTML validity of Internal Inputs in TextFilter #664
Conversation
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
just-boris
requested review from
connorlanigan
and removed request for
a team
avinashbot
approved these changes
Jan 24, 2023
just-boris
changed the title
Codecov ReportBase: 92.98% // Head: 92.98% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #664 +/- ##
=======================================
Coverage 92.98% 92.98%
=======================================
Files 574 574
Lines 16781 16781
Branches 4631 4631
=======================================
Hits 15603 15603
Misses 1101 1101
Partials 77 77
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reverts #658
The same issue was fixed by another PR #653. The #653 approach is preferred because it is more precisely scoped to the component which required a fix