Optimisation: bindTable should use DocumentFragment
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- PHP
- Stars
- 18
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I think there can be a lot of speed improvements made if the TRs are added to a fragment first, and then the fragment is added to the table.
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 locating the bindTable entry point and read how table rows are currently added. Measure or inspect the existing row-insertion path, then determine whether building rows in a DocumentFragment changes the intended output; done means the table still renders correctly with the proposed batching approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- web-dev
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100