WordPress / WordPress/php-toolkit
Steps parity with TypeScript Blueprints
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 61
- Forks
- 21
- Avg merge
- 19h 34m
- Merged PRs (30d)
- 7
Description
Pre-existing Blueprint steps should be implemented in the PHP version of the library
Backward Compatibility may not make sense for steps like login as it's unclear what that would mean in native PHP CLI environment, but steps like cp or activatePlugin should continue to work.
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the PHP Blueprint step implementations and their TypeScript Blueprint counterparts. Compare the existing steps, especially cp and activatePlugin, while checking whether steps such as login apply to a native PHP CLI environment; done means applicable pre-existing steps work in PHP with the intended compatibility behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, typescript
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100