WordPress / WordPress/wordpress-playground
Propose PRs for the projects that are now patched ad-hoc
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2k
- Forks
- 462
- Avg merge
- 18h 44m
- Merged PRs (30d)
- 33
Description
Let's start Pull Requests to improve the projects WordPress Playground is currently patching ad-hoc:
These patches are not specific to the WordPress Playground project, they enable either WebAssembly compatibility or browser compatibility.
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 reviewing the referenced sections of src/php-wasm/wasm/Dockerfile and src/wordpress-playground/wordpress/Dockerfile, then identify what each ad-hoc patch changes for WebAssembly or browser compatibility. Compare the PHP, SQLite, WordPress, and WordPress SQLite plugin cases and determine the scope of separate upstream PRs. Done means the relevant projects have proposed PRs addressing these non-project-specific patches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php, sqlite, wasm, wordpress
- Domain
- backend, databases, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 22/100