rich-text: no-string-literals fix #32142
Merged
Conversation
This file contains 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
aristath
force-pushed
the
fix/no-string-literals/rich-text
branch
from
5ecc73b to
8921ba7
Compare
|
Size Change: -11 B (0%) Total Size: 1.86 MB
ℹ️ View Unchanged
|
aristath
force-pushed
the
fix/no-string-literals/rich-text
branch
from
8921ba7 to
08e7b1b
Compare
aristath
force-pushed
the
fix/no-string-literals/rich-text
branch
from
08e7b1b to
e2f5959
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Fixes eslint warnings in the rich-text package, replaces string literals with store definitions.
Part of #27088.
How has this been tested?
npm run lint-js packages/rich-text/no longer throws warnings for string literalsChecklist:
*.native.jsfiles for terms that need renaming or removal).