[Content]: Core concepts are referenced but not explained fully/clearly (tracked/reactive scopes and ownership)
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- MDX
- Estrellas
- 292
- Forks
- 361
- Merge medio
- 7 h 51 min
- PR fusionados (30 d)
- 1
Descripción
📚 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
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Empieza leyendo la sección tracking-changes y las páginas de referencia create-root, get-owner y run-with-owner. Identifica dónde se mencionan actualmente tracked/reactive scopes y ownership, y documenta qué son, cómo funcionan y por qué son importantes, incluidos los effects, computations y el comportamiento de JSX enumerados.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Área
- documentation
- Tipo de issue
- Documentación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100