* 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
* 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
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.
Sam Seay
Joshua T Flowers
Christopher Allford
RJChow