processing / processing/p5.js-web-editor
p5.js version
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 1.7k
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 8
Description
@catarak @lmccart and I discussed this on a call yesterday. At some point in the future we'd like to have a library management system (#4), but for now we need a simple way to keep the p5.js version referenced in index.html up-to-date. We would not change index.html in existing projects (or "duplicated" projects) but would simply use the current p5.js version (0.5.4 at the time of filing this issue) whenever a "new" project is created.
@lmccart can you remind us what the url is to check the current p5 version? It could be checked something like once a day or each time "new" is clicked.
Did I get this right?
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
Start by tracing the new-project flow and how index.html is generated or selected. Determine how the current p5.js version can be checked, then verify that newly created projects use it while existing and duplicated projects remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100