…xed components. We can now edit the presentation of the individual components of the donations block. Save is not working, some styles are missing, and other basic behaviours and checks are also missing.

The coverage report started taking an extra 10 minutes after
packages/my-jetpack added JS tests because it was reporting coverage for
all of WordPress that was brought in via WorDBless. Exclude that by
default.

Also exclude the `jetpack_vendor/` directory from
packages/composer-plugin for good measure.

Co-authored-by: Brandon Kraft <[email protected]>

Co-authored-by: Jeremy Herve <[email protected]>

When creating a JS package, the CLI is pre-filling the test-coverage
script with a call to `nyc`. But it wasn't also pre-adding a dependency
on nyc, resulting in coverage not working for several packages.

Also, add the missing dep to those packages.

* fix issue with output folder creation

* [not verified] Add API and scripts

* add changelog

* [not verified] Add presisting Model class and use it all over the API

* Exclude from PHPCS for now

* Remove package from exclude list

* Require PHP 8.0

* minor additions

* Use the correct composer.json rules for requiring php 8

* Update projects/packages/analyzer/scripts/jp-analyze-parallel.php

Co-authored-by: Brad Jorsch <[email protected]>

* address feedback

* some more feedback

* update result generation logic

* Add generic query params parser class

* Add plugin downloader class

* use query params in analyze controller

* download requested versions of a plugins for scan

* Update projects/packages/analyzer/scripts/jp-analyze-parallel.php

Co-authored-by: Brad Jorsch <[email protected]>

* Update projects/packages/analyzer/src/api/class-plugin-downloader.php

Co-authored-by: Brad Jorsch <[email protected]>

* update error message

* Some changes to address issues on linux

* improve not implemented output

* fix an issue with empty $folder_name

* Address racing issue

* implement missing deserialization routines

* Update projects/packages/analyzer/scripts/jp-analyze-parallel.php

Co-authored-by: Brad Jorsch <[email protected]>

* move phpcs rule definitions around

* Use a PHP way to remove folders

* replace only first occurance of the folder in zip

* Fix PHPCS configuration 🤦

* Introduce load_differences() API

Co-authored-by: Brandon Kraft <[email protected]>
Co-authored-by: Brad Jorsch <[email protected]>

* my-jetpack: check user connectivity before to hit wpcom

* changelog

…t from connection js-package (#22480)

…ntime (#22265)

Co-authored-by: Jeremy Herve <[email protected]>

…nspector. Refactored directory structure. Added controls for the donations block. Merged all the views into a single view.

… on the front end of the site.

…card (#22486)

…t Card (#22475)

* [not verified] my-jetpack: set product param as required

* [not verified] my-jetpack: change slightly product endpoint changes

* [not verified] my-jetpack: add resolver for getProduct() selcetor

* [not verified] my-jetpack: janitorial - unify fetching action handling

* [not verified] my-jetpack: add isFetching() product selector

* [not verified] my-jetpack: update hook isFetching prop handling

* [not verified] my-jetpack: handling isFetching state in Product card

* [not verified] my-jetpack: dispatch product error action when something gets wrong

* [not verified] my-jetpack: change /site/products/$product response shape

* [not verified] my-jetpack: set the req method when activating/deactivating product

* [not verified] changelog

* [not verified] Cleaning up the API and fixing tests

* [not verified] my-jetpack: provide data to boost product card

* [not verified] my-jetpack: fix reducing product fetching state

* [not verified] my-jetpack: fix reducing product errors

Co-authored-by: leogermani <[email protected]>

* Reduced the data set for Search Sync tests.

* Search: allow the Search team to approve changes to the package

* Exclude the Search package from main package rule

This will allow the Search team review access.

* [not verified] my-jetpack: reduxify notices

* [not verified] my-jetpack: add custom hooks to deal with notice

* [not verified] my-jetpack: render global errors

* [not verified] update dependencies

* [not verified] changelog

* [not verified] my-jetpack: update composer

* update composer loc file

* my-jetpack: update product plugin absent state

* my-jetpack: connect CRM with the data provider

* chanelog

* fix typo

…n clicks (#22483)

* Create new plugins installer package

* Use plugins installer package

* add textdomain to composer json

* add new package to renovate ignore

* add changelogs

* update lock file

* remove file from exclude list

* plaease linter

* remove debug

* Update projects/packages/plugins-installer/src/class-jetpack-automatic-install-skin.php

Co-authored-by: Brad Jorsch <[email protected]>

* Update projects/packages/plugins-installer/src/class-jetpack-automatic-install-skin.php

Co-authored-by: Brad Jorsch <[email protected]>

* remove package.json

* add stub files

* add since tag to stub files

* namespace the new package classes

* [not verified] revert automatic linter changes

* [not verified] revert automatic linter changes

Co-authored-by: Brad Jorsch <[email protected]>

* Update CHANGELOG and readme.txt for release

This is the existing logic from tools/find-project-deps.php,
tools/get-build-order.php, and .github/files/list-changed-projects.php,
rewritten in JS. It also has a little more flexibility as far as
processing only a subset of projects.

One difference is in the unused composer.json `.extra.dependencies`
array: it will want that to instead be an object holding
`.extra.dependencies.test` and `.extra.dependencies.build`.

Then remove the old scripts in favor of the new command.

* introduce safe functions to check plugin status

* changelog and version bumps

* Add a disclaimer to jt-up

* Update docs

Co-authored-by: Derek Smart <[email protected]>

…22524)

…22270)

Co-authored-by: Manish Mishra <[email protected]>
Co-authored-by: Jeremy Herve <[email protected]>

…22508)

Redesign the "Safe Mode" admin bar button.

Co-authored-by: sdixon194 <[email protected]>

* install plugin from my jetpack product

* changelog

…2534)

)

* Admin: update upgrade links to use new instertials when possible

We've introduced new in-admin screens to promote upgrades; let's use them instead of directly linking to the checkout screen in Calypso, when possible. It's worth noting that for some of our upgrades (ads / Google Analytics), we do not have dedicated screens yet, so we'll continue to link to Calypso for those.

* AUpdate VideoPress upgrade link too.

* Remove unneeded prop

It's no longer used since #21006.

* Update PlanIcon.plan prop type

Co-authored-by: Samiff <[email protected]>

This lays some groundwork for future PRs that will run builds in
parallel, prefixing each line output with the appropriate slug.

The helpers in `helpers/tasks/installProjectTask.js` weren't all that
helpful anymore. Instead we provide some lower-level functions in
`helpers/install.js` that can be built upon for the slightly different
future requirements of install versus build.

Install no longer confusingly reports that it's installing pnpm
dependencies for every package being installed, instead doing a single
`pnpm install` task at the top level.

Install no longer behaves weirdly when passed both `--root` and `--all`.

Build gets an `--all` option (because it was easy to add), and an option
to skip the `pnpm install`.

Build also handles its own output in verbose mode (rather than using
listr-verbose-renderer) in preparation for parallel builds.

Due to the abstracting of `jetpack install --all` and `jetpack build
packages`, those commands now also accept multiple packages on the
command line.

* Build: remove unneeded files from packages' production builds.

…rom myJetpackInitialState (#22536)

Co-authored-by: Jeremy Herve <[email protected]>

Co-authored-by: Brandon Kraft <[email protected]>

…#22419)

Co-authored-by: Jeremy Herve <[email protected]>

…ls. (#22421)

Co-authored-by: Jeremy Herve <[email protected]>

Co-authored-by: Jeremy Herve <[email protected]>

Co-authored-by: Jeremy Herve <[email protected]>

* Force requests to restart when WPCOM reports it doesn't know them

* Update composer to prevent further conflict errors

* More reliable checks for whether a site is connected, and awaiting connection

* Mock out speed scores for all tests not explicitly about speed scores

* Extend timeout on speed score test

* changelog

* Update composer.lock for boost

* Mount e2e mock plugin in Docker instead of copying it

* [not verified] Enforce a maximum number of restarts on speed score requests

* Remove execDockerShellCommand; no need to add methods we're not using

* Fix couple of tests

p1643270965319300-slack-C016BBAFHHS
p1643274426361100-slack-C016BBAFHHS

* Add quotes to connection for consistency

* Fix: Failing e2e test due to double-await for connection

Props @adimoldovan for tracking down the issue!

Co-authored-by: Mark George <[email protected]>
Co-authored-by: pyronaur <[email protected]>
Co-authored-by: Adnan Haque <[email protected]>

* Mock new global variable myJetpackRest in unit tests

* Add changelog

* [not verified] my-jetpack: add useMyJetpackConnection() simple hook

* [not verified] my-jetpack: use custom hook to deal with connection

* [not verified] changelog

* [not verified] my-jetpack: when the site is not connected, redirect to the Jetpack dashboard.

* [not verified] my-jetpack: do not render app when no site connected

* [not verified] my-jetpack: fix rebasing issues

* [not verified] my-jetpack: add options to useMyJetpackConnection() hook

* [not verified] my-jetpack: redirect to Jetpack dashboard when no connection

* [not verified] my-jetpack: add useMyJetpackConnection() simple hook

* [not verified] my-jetpack: use custom hook to deal with connection

* [not verified] changelog

* [not verified] my-jetpack: when the site is not connected, redirect to the Jetpack dashboard.

* [not verified] my-jetpack: do not render app when no site connected

* [not verified] my-jetpack: fix rebasing issues

* [not verified] my-jetpack: add options to useMyJetpackConnection() hook

* [not verified] my-jetpack: redirect to Jetpack dashboard when no connection

* [not verified] my-jetpack: expose redirectUrl from useMyJetpackConnection hook

* [not verified] my-jetpack: set url in no conenction global error

* [not verified] my-jetpack: check whether user is conected before to redirect

* [not verified] my-jetpack: check user when no render because lack of connection

* [not verified] my-jetpack: simplify connection status cmp

* [not verified] my-jetpack: check only site when redirect because of connection

* [not verified] my-jetpack: restore redirectUri prop to connection component

* changelog

* fix tests

* updating dependencies and lock files

It was dropping the first project, causing needed tests to be skipped.

Co-authored-by: oskosk <[email protected]>

* Move Critical CSS Recommendation to own class

* Add changelog

* After recommendation refactor fix

Signed-off-by: pyronaur <[email protected]>

* Move constants filter inside CSS Recommendations class

Signed-off-by: pyronaur <[email protected]>

* Move on_uninstall

Signed-off-by: pyronaur <[email protected]>

* Refactor Critical CSS recommendation

Added Notification base class and extended to Recommendation class to cleanup the current design.

* Remove legacy Recommendation

* Refactor get notifications for abstraction

* Refactor inheritance aware notification key

* Refactor module constructors to on_prepare

Change module constructors to on_prepare so that the actions calls are not duplicated.

* Remove non-existing class from comment

Signed-off-by: pyronaur <[email protected]>

* Refactor Notifications to OptionsArray

* Dump generation related functions into Generator class

Signed-off-by: pyronaur <[email protected]>

* Go ahead, make a mess.

Creating an absolute mess out of the Critical CSS Class.

Signed-off-by: pyronaur <[email protected]>

* Re-add handle_css_proxy

Signed-off-by: pyronaur <[email protected]>

* Move: api_get_critical_css_status

Signed-off-by: pyronaur <[email protected]>

* Add critically bad comments

Signed-off-by: pyronaur <[email protected]>

* Remove module is_initialized

* Clarify method name: get_current_request_css

Signed-off-by: pyronaur <[email protected]>

* Create a dedicated method to display Critical CSS

Signed-off-by: pyronaur <[email protected]>

* Whoops - wrong condition.

`! is_admin()` guard clause was protecting against showing Critical CSS anywhere else but the admin :)

Signed-off-by: pyronaur <[email protected]>

* Move & De-duplicate AMP Compatibility

Signed-off-by: pyronaur <[email protected]>

* Refactor AMP conditions to separate file

* Move Providers

Move providers to `critical-css/path-providers/providers`

Signed-off-by: pyronaur <[email protected]>

* Create a class to manage Critical CSS Paths

Signed-off-by: pyronaur <[email protected]>

* Add module initialized action

* Move generator out of the main Critical CSS class

Signed-off-by: pyronaur <[email protected]>

* Fix missing providers

Signed-off-by: pyronaur <[email protected]>

* Remove the need to inject providers

Signed-off-by: pyronaur <[email protected]>

* Clean up backslash

Signed-off-by: pyronaur <[email protected]>

* Remove an unused import

* Remove comments

* Move recommendations out of the main Critical CSS Class

* Clean up recommendations class

* Clean up Options and Recommendations

* Reorganize REST_API Class

* Simplify REST API Class

* Add a regression note (!)

* De-nest config array

* Few more comment cleanups

As I browse tearing my hear out one by one, I also pluck out a few unnecessary comments.

* Experiment: Abstract API Class

* Implement `request-generate` using Boost_API

* Generator Success & Error endpoints

* Fix typos, simplify endpoint method

* PSR4

* Move Recommendations to Boost API

* API -> REST_API

* Add nonces to REST API

* Speculative generality

* Cleanup

* Fix missing nonce regression

While refactoring, we had to forget for a moment a use case where Nonces weren't initialized if the module isn't active. This is now fixed again.

* Auto-fix phpcs errors

* Add Docblock comments

* Update Classes to PascalCase

* Refactor amp compatibility

Refactor amp compatibility functionality to a class to remove the usage of anonymous function and the usage of `use` keyword.

* Fix class module unit test

* Revert Update Classes to PascalCase

* Improve how the option list object is described

* Clarify the collection code a bit

* Disable autoloading on recommendations

* Clarify collection comments

* Clean-up comments

* Improve comments and phpDoc hints

* Revert "Add Docblock comments"

This reverts commit d2e693e.

# Conflicts:
#	projects/plugins/boost/app/lib/class-options.php
#	projects/plugins/boost/app/modules/critical-css/Display_Critical_CSS.php
#	projects/plugins/boost/app/modules/critical-css/Recommendations.php
#	projects/plugins/boost/app/modules/critical-css/rest-api/Boost_API.php

* Config ID's aren't used anymore

* Remove unused method

* Remove unmodified methods

* Refactor the config class

* Replicate lazy images in both Jetpack and Boost

* Remove dead code

* Move connection related code to connection class

* Remove unused meta tag

* Typo

* Refactor Critical CSS REST API

* Update the namespaces to match the new file structure

* Restore behavior: ensure the module is initialized

* Revert "Restore behavior: ensure the module is initialized"

This reverts commit 6b3f987.

Turns out we don't need to restore this behavior anymore because our API Requirements have changes after many plugin iterations.

* Remove todos - no longer a required feature

* Move Critical CSS REST API files

* Boost_API -> REST_API

* Simplify Critical CSS REST API initialization

* Cleanup

* A step towards a modular REST API

* A step towards modular modules

* Move module filtering to a dedicated method

* Rename Module to Module_Toggle

* Create a Module calss that deals with module setup

* Make REST_API Route registration more elegant

* Move module toggling to the the new REST API format

* Move modules out of main plugin class

* Update comments

* Cleanup comments

* Mass rename

After chat with Adnan, we decided that a couple of things are pretty unclear - this is a step towards giving classes better names

* Toggle_Module -> Optimization_Status

* Modules -> Features & Optimizations

* Silence php8 error

* Unit test fix

* Fix module tests

* phpcs autofix

* Fix phpcs errors & warnings

* Clean up optimization status tracking

* state -> status

* Simplify uninstall

* Add missing namespaces

* Fix CLI for e2e tests

This is not a permanent fix, but I just need e2e tests to run right now

* Seamlessly migrate to the new options format.

* Protect against recursion

* Add Has_Setup and Setup classes

Add an interface and a class to ensure that a class is going to need to be set-up at a later point in time via hook.

* Improve how Optimization objects are initialized

* [not verified] Fix: return statement was left over after refactoring

* Allow any unused parameters which start with _, to allow for implementing interfaces without warty comments

* Catch errors that occur when queuing up Critical CSS generation, so the UI doesn't freeze if the server 500s

* Skip lazy-image tests until reinstated later

Co-authored-by: Karthik Bhat <[email protected]>
Co-authored-by: Mark George <[email protected]>

* components: re-organize stories by project/js-pgk

* changelog

* my-jetpack: tweak product card status dims

* changelog

* my-jetpack: use var to define status height

* my-jetpack: fix issue when setting style via var

* remove unused css var

* my-jetpack: check data when analytics initializes

* my-jetpack: fix ProductCard stories

* changelog

* my-jetpack: fix tracking event when activating product

* changelog

* [not verified] Track user clicks on disconnect dialog modal

* Fix and add some unit tests

* Changelog

* changes based on review comments

- rename stay connected handler
- move all click tracking code to step-disconnect

* Update based on comments

- fix tests to loop and be less brittle
- stop constructing event names programmatically
- some formatting

* version fixup script

* Creates the Product abstract class and adds CRM

* uses new class to fetch CRM info

* add Hybrid product abstraction and Backup

* changelog

* [not verified] Creates the Product abstract class and adds CRM

* [not verified] uses new class to fetch CRM info

* [not verified] add Hybrid product abstraction and Backup

* [not verified] changelog

* Fix tests

…ns (#22546)

)

Co-authored-by: Jeremy Herve <[email protected]>

Co-authored-by: Jeremy Herve <[email protected]>

…ss (#22594)

* [not verified] my-jetpack: add long description product field

* [not verified] my-jetpack: call Back::get_info() when providing data

* changelog

* My Jetpack: time to connect all product cards

* changelog

When multiple projects are being built, build them in dependency order
(i.e. each project's dependencies are build before the project is).

If the new `--deps` option is specified, include all dependencies of the
specified projects in the build.

We previously relied on wpcom, which unfortunately won't work here; it does end up being defined even on Jetpack sites, because of the additional scripts from WordPress.com that are enqueued in the admin.

Co-authored-by: Samiff <[email protected]>

* [not verified] add module products

* [not verified] add new required methods

* [not verified] changelog

* remove wrong annotation

* remove deprecated annotation

* my-jetpack: add Jetpack Dashboard color

* changelog

* my-jetpack: remove getProduct() resolver

* changelog

* add user connection requirement to product info

* update test