Resolve `view_to_component` limitations
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
Línea de trabajo
Start by tracing the view_to_component entry point named in the issue. The issue lists HTTP-method handling, ReactPy event attachment, and same-domain hyperlink interception as separate limitations, but names no files or tests; done would require defining and implementing the intended iframe-like behavior for these cases.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Current Situation and Proposed Actions
There are currently several limitations of using view_to_component.
- Requires manual intervention to change HTTP methods to anything other than
GET.- The initial HTTP request will probably always have to be
GET, but it might be reasonable to automatically handle other kinds of HTTP methods depending on what the user clicked on. - Realistically, the end goal is to make
view_to_componentbehave as similarly to an iframe as technologically possible.
- The initial HTTP request will probably always have to be
- ReactPy events cannot conveniently be attached to converted view HTML.
- It might make sense to give the user some kind of interface to "query select" certain rendered items, and attach ReactPy event functions to them.
- Has no option to automatically intercept click events from hyperlinks (such as
<a href='example/'></a>).- All hyperlinks that point to the current domain should probably be intercepted by ReactPy and rendered via
view_to_component. - Realistically, the end goal is to make
view_to_componentbehave as similarly to an iframe as technologically possible.
- All hyperlinks that point to the current domain should probably be intercepted by ReactPy and rendered via
- Lenguaje dominante
- Python
- Estrellas
- 357
- Forks
- 22
- Merge medio
- 10 h 31 min
- PR fusionados (30 d)
- 2
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
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.
Más de reactive-python/reactpy-django
-
Add coverage tests Abiertocomplexity: 3 (low) priority: 3 (low) type: ci
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
-
complexity: 1 (high) priority: 1 (high)
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
-
complexity: 2 (medium) priority: 3 (low)
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
-
`pyscript_router` component Abiertocomplexity: 1 (high) priority: 2 (moderate)
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
-
complexity: 2 (medium) priority: 2 (moderate) type: investigation
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
Todos los issues de reactive-python/reactpy-django
Issues similares
-
documentation help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
simonw/sqlite-utils#872 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100