Needed mutation detection improvements
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.2k
- Forks
- 202
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 3
Description
With #595 merged, We'll move these todo items from the PR to issues as a reminder to look at them before releasing Solara 2.0.
TODO:
- Trigger calls to check_mutations() from several places: after an event handler (requires a change in reacton) and after a component run.
- We probably do not want two equals function in solara/reacton, reconcile this.
- #983
- support reactive.get(copy=True) to always get a copy, even when _CHECK_MUTATIONS is False
- Do we need support reactive.get(reference=True) to always get a reference, or is the opt-out enough?
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 reviewing the mutation-detection changes in merged PR #595 and the TODO list in this issue. Trace check_mutations() around event handlers and component runs, then review reactive.get() and the two equals functions in Solara/reacton. Done means the trigger points and copy/reference API decisions are resolved and the resulting behavior is covered before Solara 2.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100