Maybe color shouldn't map to textfont.color
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 2.7k
- Forks
- 641
- PR merge metrics
- No merged PRs in 30d
Description
plotly.js seems to impose smart defaults for text color anyway, for example:
Note that if you change split to color, you can't see the text!!
zoo_dat <- tibble::tibble(
animal = rep(c('giraffes', 'orangutans', 'monkeys'), 2),
count = c(20, 14, 23, 12, 18, 29),
zoo = rep(c('SF Zoo', 'LA Zoo'), each = 3)
)
plot_ly(zoo_dat) %>%
add_bars(
x = ~animal,
y = ~count,
text = ~count,
textposition = "auto",
split = ~zoo,
stroke = I("black")
)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the supplied plot_ly/add_bars example in R and inspect how plotly.js assigns textfont.color when bars use split = ~zoo. Compare the output after changing split to color; done means the text remains visible under the reported smart-default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, r
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100