Skip to content
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

Enhance/press7 60 jetpack boost #25

Merged
merged 27 commits into from
Dec 14, 2024

Conversation

AleTorrisi
Copy link
Contributor

Proposed changes

This branch introduces the new section "Advanced settings" which includes main Jetpack boost options, so that they can be set by Bluehost panel and synchronized with Jetpack panel too.

Type of Change

  • Bugfix (non-breaking change which fixes an issue)
  • [x ] New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Video

Screen-2024-11-11-134622.mp4

Checklist

  • [x ] I have read the CONTRIBUTING doc
  • I have viewed my change in a web-browser
  • [x ] Linting and tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Fix: avoid import of unused component
@chrisdavidmiles
Copy link

@arnavchaudhary We need a PR on this

Copy link
Member

@arunshenoy99 arunshenoy99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @AleTorrisi, thank you for the PR! This looks fantastic, especially since it's your first time working on this codebase. I added a few small comments and optimizations. Please take a look and let me know if they make sense.

Other than that:

  1. Let's ensure we run the wp-scripts linter on the JS files.

  2. Let's ensure we have a newline at the end of each file for consistency.

  3. Here's what I am seeing on my local environment with your changes. If I’m missing something, that’s all OK, but please reconfirm if these buttons look correct:

    image

Let me know your thoughts or if anything needs further clarification ✌️

components/performance/index.js Outdated Show resolved Hide resolved
includes/Performance.php Outdated Show resolved Hide resolved
includes/Performance.php Outdated Show resolved Hide resolved
includes/RestApi/JetpackController.php Outdated Show resolved Hide resolved
components/advancedSettings/JetpackBoost/index.js Outdated Show resolved Hide resolved
components/advancedSettings/JetpackBoost/index.js Outdated Show resolved Hide resolved
components/performance/index.js Outdated Show resolved Hide resolved
includes/Performance.php Outdated Show resolved Hide resolved
@wpscholar wpscholar requested review from bradp and removed request for wpscholar November 16, 2024 17:38
@AleTorrisi
Copy link
Contributor Author

Hey @AleTorrisi, thank you for the PR! This looks fantastic, especially since it's your first time working on this codebase. I added a few small comments and optimizations. Please take a look and let me know if they make sense.

Other than that:

  1. Let's ensure we run the wp-scripts linter on the JS files.
  2. Let's ensure we have a newline at the end of each file for consistency.
  3. Here's what I am seeing on my local environment with your changes. If I’m missing something, that’s all OK, but please reconfirm if these buttons look correct:
    image

Let me know your thoughts or if anything needs further clarification ✌️

  • JS Lint has been performed in this commit.
  • I can't replicate the issue about newline at the end of the file, it exists on my side
  • I can see just one button by my side, please launch "npm run build" and empty the browser cache.

arunshenoy99
arunshenoy99 previously approved these changes Nov 20, 2024
Copy link
Member

@arunshenoy99 arunshenoy99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the performance test is failing for something related to accessibility. Other than that looks good to me. Thanks! @AleTorrisi

'wp-module-performance'
),
jetpackBoostCriticalCssTitle: __(
'Optimize Critical CSS Loading (manual)',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's "manual" mean in this case? cc @chrisdavidmiles

Copy link
Contributor

@bradp bradp Nov 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be the difference between paid Jetpack Boost vs free, on paid this is automatic.

arunshenoy99
arunshenoy99 previously approved these changes Dec 12, 2024
Copy link
Member

@arunshenoy99 arunshenoy99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, the test is failing because the workflow is not picking up the new installer dependency. This should not be an issue when we create a bump PR in the web/mojo plugin.

@arunshenoy99 arunshenoy99 changed the base branch from main to release/v2.1.0 December 14, 2024 12:56
@arunshenoy99 arunshenoy99 merged commit 150f392 into release/v2.1.0 Dec 14, 2024
5 of 7 checks passed
@arunshenoy99 arunshenoy99 deleted the enhance/PRESS7-60-jetpack-boost branch December 14, 2024 12:57
@arunshenoy99 arunshenoy99 mentioned this pull request Dec 14, 2024
14 tasks
@arunshenoy99 arunshenoy99 restored the enhance/PRESS7-60-jetpack-boost branch December 16, 2024 09:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants