-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quality: Promote lint rule to error when validating store string literals #32537
Conversation
There is still 6 errors to fix:
I figured out that
gutenberg/packages/server-side-render/src/index.js Lines 19 to 20 in 8d5139d
It's worth noting that
I see it used with the following blocks:
|
Size Change: +4 B (0%) Total Size: 1.04 MB
ℹ️ View Unchanged
|
@youknowriad, is 974557a correct? I would appreciate your guidance here. |
@gziolo that commit looks correct to me 👍 |
974557a
to
6f9ba12
Compare
It looks like it only needs to provide the current post id when in the context of the post type editor as introduced in #9323. It looks like something that could be read from the context rather than through the selector. |
6f9ba12
to
58aab25
Compare
Description
Fixes: #27088.
This is the last step to replace hardcoded store keys with store definitions. This PR promotes
@wordpress/data-no-store-string-literals
ESLint rule to the error level.How has this been tested?
npm run lint-js -- --quiet
Types of changes
Code quality.