WordPress / WordPress/grunt-patch-wordpress
Deprecate grunt-patch-wordpress
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 51
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
grunt-patch-wordPress has been an amazing tool, but it's time for it to move on. In order to do that, we need to get a successor in place. For that, we need to:
- Remove the grunt dependency
- Migrate the tests from mocha to jest ( see: https://gziolo.pl/2017/10/25/migrating-to-jest-test-runner/ )
- Use the wordpress/gutenberg scripts and styles
- Move the codebase over to wordpress/gutenberg
- ???
- Celebate the future.
It's possible that this repo can serve as a thin grunt wrapper around the replacement script.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test path is named; begin by inventorying the package configuration, Grunt entry points, and current Mocha tests. Review the requested Jest and WordPress Gutenberg migration boundaries, then clarify whether this repository becomes a thin Grunt wrapper; done requires an agreed successor and validated migration plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wordpress
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100