[Content]: Core concepts are referenced but not explained fully/clearly (tracked/reactive scopes and ownership)
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- MDX
- Sterne
- 292
- Forks
- 361
- Ø Merge
- 7 Std. 51 Min.
- Gemergte PRs (30 T.)
- 1
Beschreibung
📚 Subject area/topic
Tracking scopes and ownership
📋 Page(s) affected (or suggested, for new content)
https://docs.solidjs.com/concepts/intro-to-reactivity#tracking-changes
And anywhere that mentions something like "signals must be accessed within a tracked/reactive scope"
https://docs.solidjs.com/reference/reactive-utilities/create-root
https://docs.solidjs.com/reference/reactive-utilities/get-owner
https://docs.solidjs.com/reference/reactive-utilities/run-with-owner
📋 Description of content that is out-of-date or incorrect
There are important concepts in solid like the idea of tracked/reactive scope or ownership that are mentioned but there isn't a place that clearly explains them.
Tracked/Reactive Scope
Signal updates will only be reacted to if they are accessed in a reactive or tracked scope, however I don't think there is a place that clearly outlines what all of the reactive scopes are.
Many examples just say to use createEffect or imply that JSX is a reactive scope but there isn't a place that goes through all of them or explains why the JSX template is a reactive scope.
- all of the different effects/computations
- createRoot (I don't fully understand how this works but in the OG docs it says the render function uses this to create the tracked scope for the app)
Owners
- What is an owner?
- What does it do?
- How does ownership work in solid?
- Why are they important?
🖥️ Reproduction in StackBlitz (if reporting incorrect content or code samples)
No response
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne mit dem Lesen des Abschnitts tracking-changes und der Referenzseiten create-root, get-owner und run-with-owner. Ermittle, wo tracked/reactive scopes und ownership derzeit erwähnt werden, und dokumentiere anschließend, was sie sind, wie sie funktionieren und warum sie wichtig sind, einschließlich der aufgeführten effects, computations und des JSX-Verhaltens.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Bereich
- documentation
- Issue-Typ
- Dokumentation
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100