-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Try @wordpress/scripts #358
Open
jffng
wants to merge
16
commits into
amnestywebsite:develop
Choose a base branch
from
jffng:try/wordpress-scripts
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
jffng
commented
Aug 9, 2024
@@ -6,33 +6,35 @@ let subMenus = []; | |||
// if menu has lost focus inadvertently, restore it | |||
const setupFocusTrap = () => { | |||
const lastMenuItem = pageHeader.querySelector('.mobile-menu > ul > li:last-of-type'); | |||
const menuItemClassList = `.${Array.from(lastMenuItem.classList).join('.')}`; | |||
let previousFocus; | |||
if ( lastMenuItem ) { |
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.
This is kind of an unrelated change, but I was getting a scripting error since this was undefined in my test setup.
jffng
commented
Aug 9, 2024
jffng
commented
Aug 9, 2024
@@ -114,7 +114,8 @@ class DisplayAuthor extends Component { | |||
|
|||
api | |||
.getPostsFromAuthors(requestArguments, value) | |||
.then((data = [], i, xhr) => { // eslint-disable-line | |||
.then((data = [], i, xhr) => { |
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.
These changes were the result of running yarn lint --fix
.
jffng
force-pushed
the
try/wordpress-scripts
branch
from
August 9, 2024 17:08
e8dff12
to
4e1d2d8
Compare
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
This PR migrates the build scripts to
@wordpress/scripts
to compile the theme as is. The idea is to simplify the build configuration, and provide an incremental change to allowing the blocks to be upgraded.Ref: #285
Steps to test:
cd private
rm -rf node_modules
yarn && yarn build
Considerations:
I think the main benefit to this PR is it cuts down on the projects development dependencies. But if you do go ahead with moving the blocks to a separate plugin in the near term, then maybe this PR is not as relevant or useful.