[Content]: Core concepts are referenced but not explained fully/clearly (tracked/reactive scopes and ownership)
Nessuno ha ancora preso questa issue.
- Lingua principale
- MDX
- Stelle
- 292
- Fork
- 361
- Merge medio
- 7h 51m
- PR unite (30g)
- 1
Descrizione
📚 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
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia leggendo la sezione tracking-changes e le pagine di riferimento create-root, get-owner e run-with-owner. Mappa dove vengono attualmente menzionati tracked/reactive scopes e ownership, quindi documenta cosa sono, come funzionano e perché sono importanti, inclusi gli effects, le computations e il comportamento JSX elencati.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Ambito
- documentation
- Tipo di issue
- Documentazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100