Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Issue with NA handling in scatter plots: Two NAs per category cause incorrect line connection

Ouverte
  • Quelque chose ne va pas ?
#2,419 3 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
r
Domaine
data-visualization

Piste de recherche

Commencez par exécuter l’exemple reproductible de plot_ly() dans l’issue et comparez la sortie avec et sans hovertemplate et split = ~Category. Suivez la manière dont l’appel R à plotly représente les valeurs NA et les traces de catégories, puis vérifiez que exactement deux NA par catégorie produisent un espace visible sans nécessiter split ni supprimer hovertemplate.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Issue Summary

When using plot_ly() in R with a scatter plot (mode = "lines+markers"), missing (NA) values are expected to create gaps in the line plot. However, if exactly two NA values exist per category, the missing values are incorrectly connected by a line instead of creating a gap.

Interestingly, when the hovertemplate is removed, the line plot behaves as expected (i.e., creating a gap for NA values). This issue only occurs when there are exactly two NA values per category; the code works with any other number of NA values.

Additional Discovery:
The issue is resolved if I include the argument split = ~Category, but I cannot find documentation for split in Plotly, which makes me think it may be deprecated. Moreover, when the hovertemplate is removed, the inclusion of split does not work as expected and does not resolve the issue.

Reproducible Example

The following R code demonstrates the issue:

library(plotly)

df <- data.frame(
  Category = rep(c("A", "B"), each = 6),
  Date = c(2020, 2021, 2022, 2023, 2024, 2025, 2020, 2021, 2022, 2023, 2024, 2025),
  Value = c(10, 15, NA, NA, 20, 25, 12, 14, NA, 22, NA, 27)
)

df$Date <- factor(df$Date, levels = unique(df$Date), ordered = TRUE)

plot_ly(
  df,
  x = ~Date,
  y = ~Value,
  color = ~Category,
  type = 'scatter',
  mode = 'lines+markers',
  text = ~Category,
  hovertemplate = paste0("Date: %{x}<br>Category: %{text}")
)

Expected Behaviour

  • NA values should create a gap in the line plot, i.e., they should not be connected.
  • This works correctly when there is any number of NA values other than exactly two in any category.

Actual Behavior

  • When there are exactly two NA values per category, the missing values are incorrectly connected by a line instead of creating a gap.
  • When the hovertemplate is removed, the lines create a gap as expected.
  • The issue only arises when there are exactly two NA values per category; any other instance of NA works fine.
  • Including split = ~Category resolves the issue, but:
    • I cannot find any Plotly documentation on split, leading me to believe it may be deprecated.
    • Interestingly, when the hovertemplate is removed, including split does not resolve the issue.

Additional Notes
This seems to be an issue specifically triggered by the combination of NA handling and the hovertemplate. I would appreciate further insight on why this happens or suggestions for a workaround to preserve the gap in the case of two NA values.

System Info

R version 4.4.2 (2024-10-31 ucrt)
Platform: x86_64-w64-mingw32/x64
Running under: Windows Server 2019 x64 (build 19045)

Matrix products: default

Langage dominant
R
Étoiles
2.7k
Forks
640
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de plotly/plotly.R

Toutes les issues de plotly/plotly.R

Issues similaires

Plus d'issues R

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.