Add add_*() functions for each trace type and provide error checking
Open
Nobody has claimed this yet.
plotly.js
- Dominant language
- R
- Stars
- 2.7k
- Forks
- 641
- PR merge metrics
- No merged PRs in 30d
Description
- For example,
add_scatter()/add_bar()/etc. These would essentially be thin wrappers aroundadd_trace()with the proper type.- Throw errors for when required properties are missing. For example,
add_scatter3d()requiresx/y/z. - Throw errors for when a property is of the wrong type. See, for example, #329.
- Throw errors for when required properties are missing. For example,
@timelyportfolio this would maybe be a good exercise if you're up for it?
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 reviewing the existing add_*() wrappers and add_trace() entry point, then inspect issue #329 for the intended wrong-type validation behavior. Confirm which trace types and properties still lack checks, and define done as errors being raised for invalid property types without breaking the existing required-property checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100