-
Notifications
You must be signed in to change notification settings - Fork 219
Use the eslint config at the root of the repo #7149
Conversation
The release ZIP for this PR is accessible via:
|
Size Change: 0 B Total Size: 874 kB ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @hsingyuc thank you for this - I tested it and it's working great. Please could you remove the changes to assets/js/base/context/providers/store-notices/components/store-notices-container.js
from this PR?
@opr Thank you for catching the unrelated changes! I've updated the changes. |
Thanks @hsingyuc , sorry to be pedantic but there's a line-break deleted in ``assets/js/base/context/providers/store-notices/components/store-notices-container.js` is this on purpose? I think we can just get rid of changes to that file entirely otherwise? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, let's 🚢 it!
Eslint uses both the parent and the current repo's eslint config file. It should ignore parent .eslintrc configuration.
The change uses the eslint config at the root of the repo.
Fixes #7148
Similar PR woocommerce/woocommerce-gateway-stripe#2414
Screenshots
Testing
woopay
docker instancewoocommerce-blocks
plugin towoopay/docker/wordpress/wp-content/plugins/woocommerce-blocks
npx eslint --debug .eslintrc.js
to see eslint is not using the config file fromwoopay
Automated Tests
Changes in this PR are covered by Automated Tests.
Do not include in the Testing Notes
WooCommerce Visibility
Performance Impact