plotly core (a community vote for a simple wrapper to plotly.js)
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- R
- Estrellas
- 2.7k
- Forks
- 641
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
Hello, long time user of plotly.R here. I thought this issue could start the discussion to split up the package into a core and a full ggplotly supported package.
As many have noted, I also started using plotly from the ggplot2 interface of ggplotly,
but as times are changing, and I am getting to understand the drawbacks of wrapping things through ggplot more,
we are moving more and more away from it.
In our RiboCrypt app, we have for optimizations reasons removed all ggplotly calls and transformed to native plot_ly() calls. We experiment with optimizations like pre-building plotly template objects, to speed up "time to user see something useful".
And since this is an app for complicated genomics, R/bioconductor is still a far better fit than python.
A problem has been the last few year that new plotly.R versions break stuff, so I have to keep version set to a version I know works. Problem is that new version needs to pass not just plotly.js tests, but also ggplotly tests for regression, so it is currently much more complicated than it needs to be.
I vote for a clean split of the package, for existing popular R package doing this, see for example the fst package, which has fst and fstcore
plotlycore: Simple wrapper to plotly.js
plotly: Uses plotlycore + ggplotly interface.
This way I think it is more safe especially for people using it for actual production apps and not just scripting.
I thought we could discuss here what people have noticed lately, what the relevant goals of current maintainers are, what resources exist to do this etc.
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 división propuesta entre un wrapper simple de plotly.js y el paquete compatible con ggplotly; después, compara el ejemplo de fst/fstcore enlazado en el issue. Revisa la estructura actual del paquete plotly.R y las responsabilidades de plot_ly(), ggplotly y regression-test. Se considera terminado cuando los maintainers hayan acordado límites concretos entre los paquetes y objetivos de implementación.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- javascript, r
- Área
- data-visualization
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Tranquilo
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100