nextcloud / nextcloud/calendar
Move ics parsing and expansion to web worker
Open
Nobody has claimed this yet.
1. to develop
enhancement
performance 🚀
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Moving ics parsing and expansion to a web worker will:
- speed up rendering in generell
- protect the user interface from freezing (when ical.js runs in an expansion related infinite loop)
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
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
The issue names no files, tests, or entry points, so first trace where ICS parsing and expansion currently run in the JavaScript application. Investigate the worker boundary and communication needed for that work. Done means parsing and expansion run in a web worker, rendering is faster, and the interface does not freeze during an expansion loop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100