* pin eslint in .syncpackrc
run `pnpm run sync-dependencies` to ensure pinned version is used across projects, then run `pnpm install` to update `pnpm-lock.yaml`
* add changelog files
ran `pnpm run --no-bail --filter='[HEAD^1]' changelog add --significance=patch --type=dev --entry='Update eslint to 8.32.0 across the monorepo.'`
* re-run `pnpm install` to fix what broke while merging
* issue-35763/fix-php-8.2-deprecation-warnings
* Declare $mockable_functions property
* Declare $mockable_classes property
* Fix deprecated usage of ${var} in strings
* Add changelog file
* Avoid using interpolation to create SQL statement
We could ignore the PHPCS error. However, ignoring the error leaves
PHPCS unable to detect future changes that may introduce unsafe
interpolation.
I think the more verbose approach is the safest approach in this
case.
* Ignore WordPress.DB.PreparedSQL.InterpolatedNotPrepared
There doesn't seem to be a way to use a variable name for the name of the table without
triggering a PHPCS error.
* Avoid interpolated passing interpolated variables to __()
* End inline comments with a full-stop
* Add @babel/plugin-proposal-class-properties to run storybook
* Add @babel/plugin-proposal-class-properties to webpack config and remove storybook env from babel config
* Add changelog
* Use downshift built in methods to handle selection of items
* Fix menu styling
* Fix removal a11y announcement
* Don't show menu without results
* Fix async example a11y
* Add changelog entry
* Deselect item in state on remove
* Fix formatting issues
* Update lock file
* Update lock file after pnpm7
* Skip lib check breaking oclif build in package-release
* Rebase again and fix up lock file
* Skip lib check in monorepo-merge
* Fix the lock
* Ignore lint
Co-authored-by: Sam Seay <samueljseay@gmail.com>
Co-authored-by: Jonathan Sadowski <sadowski@automattic.com>
* Remove -- -- from scripts that fixed issue in pnpm 6, fix a couple TS issues in sep packages
* Minor fixes to analyzer scripts and doco based on pnpm 7
* Add dompurify types to data package to avoid TS errors
* Remove pnpx in favor of pnpm exec
* Modify the code analyzer to respect pnpm version if present.
* Update instructions for running recursive lint, add comments to explain
This also adds a new command `major_minor` that contains some of the old logic of `getPluginData` to determine the latest major/minor version of WooCommerce
* Change package json commands and turbo repo config to allow for greatly simplifying running turbo
* Remove require-turbo script which was causing caching issues
* Colorize CI output from scripts
* Add missing changelog script to extend-cart-checkout-block
This replaces all `nx` commands with `turbo` commands and removes Nx from the repository. All of the `project.json` files have been removed and any commands that broke with Turborepo have been adjusted.
* Add schema
* update to new filepath
* test
* Revert "test"
This reverts commit d05a731a46.
* remove unused import
* add products and orders scanning
* escape slashes
* save
* save
* save
* test
* save
* save
* better descriptions
* moar tests
* Revert "moar tests"
This reverts commit ad552db45b.
* remove test
* better doc blocks
* check port first
* stop wp-env after operation is done
* remove ProductAttributesLookup
By default, TypeScript looks for type roots in
parent node_modules directories. We can't
do this because there are React types
that cause errors. This commit explicitly
defines the type roots for the package to avoid
that behavior.
This commit cleans up the command now that I'm
generally happy with the implementation. It should
be much easier to follow now, as well as follow
GitHub's GraphQL best-practices around sanitation.
This commit cleans up some of the action stop
handling in the merge command. I was adding
this handling to the issue transfer command and
saw the same mistakes made here.
This commit adds the skeleton for an issue transfer command.
Almost all of the functionality is implemented, but it is missing
the actual transfer of issues. I'm nervous about testing this, so
I'm going to implement the rest of the functionality first.
This contains the basic framework for our new `monorepo-merge`
command. The goal will be for this command to handle the heavy lifting
for merging repositories with full history. It will (ideally) bring any
plugin or package into the repository in a ready-to-use state.
Fixes a PHP Fatal error:
```
PHP Fatal error: Uncaught Error: Class 'Automattic\WooCommerce\MonorepoTools\Changelogger\DateTime' not found in /var/www/woo/wp-content/plugins/woocommerce/tools/changelogger/Formatter.php:143
```
* Removed Changlogger Autoload
* Changed Jetpack Changelogger Formatter Loading
Rather than using the Composer autoload, we should use the
changelogger's "filename" option to point directly at the file.
This keeps the file out of the autoloads, since it's possible that
plugins or packages may be symlinked and break the relative
path to the plugin.
Sam Seay
Leif Singer
jonathansadowski
Willington Vega
Chi-Hsuan Huang
Paul Sealock
Roy Ho
Joshua T Flowers
Christopher Allford
AnnaMag
Claudio Sanches
Christopher Allford
Jonathan Sadowski
RJChow