WordPress / WordPress/php-toolkit
Refresh Playground when new Blueprint is provided in hash
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 61
- Forks
- 21
- Avg merge
- 19h 34m
- Merged PRs (30d)
- 7
Description
Updating the Blueprint inside the URL hash playground.wordpress.net/#{"steps":[... has no effect, which is a bit annoying when iterating on Blueprints. Let's apply the new Blueprint whenever it changes like this:
addEventListener("hashchange", (event) => {});
Props to @seanmorris for the suggestion
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 in the Playground entry point that reads the Blueprint from the URL hash, then trace how the initial Blueprint is applied. Handle the hashchange event so a changed hash applies the new Blueprint; verify manually by editing the hash and confirming the Playground refreshes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100