plotly core (a community vote for a simple wrapper to plotly.js)
Personne n'a encore pris cette issue.
- Langage dominant
- R
- Étoiles
- 2.7k
- Forks
- 641
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
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.
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par lire la séparation proposée entre un wrapper simple de plotly.js et le package compatible avec ggplotly, puis comparez l’exemple fst/fstcore lié dans l’issue. Examinez la structure actuelle du package plotly.R ainsi que les responsabilités de plot_ly(), ggplotly et regression-test. Le travail est terminé lorsque les maintainers se sont mis d’accord sur des limites de package et des objectifs d’implémentation concrets.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- javascript, r
- Domaine
- data-visualization
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- Calme
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100