OpenSlides / OpenSlides/openslides-client
Motion diff and line numbering performance
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 35
- Forks
- 52
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 52
Description
This is a follow up to #3014 for preserving findings.
Problematic scenarios:
- a lot of amendments (50+) attached to a single motions
amendments to very long motions
Affected pages:
- Motion detail
- Amendment list filtering
- Amendment list entry rendering
Identified performance bottlenecks
- line numbering calculation (optimization potential very likely exhausted)
- paragraph number calculation
- (getDiff calculation)
Besides from that we could discuss if it makes sense to introduce motion text size limits for which we display a warning.
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 profiling the Motion detail, amendment list filtering, and amendment list entry rendering paths for motions with 50 or more amendments. Focus on the identified line-number, paragraph-number, and getDiff calculations, then compare results for long motions. Done means measurable improvement in these scenarios and a documented decision about whether text-size warnings are needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100