ggplot2 writer
Open
Nobody has claimed this yet.
writer
- Dominant language
- Rust
- Stars
- 554
- Forks
- 30
- Avg merge
- 17h 27m
- Merged PRs (30d)
- 8
Description
I think we all agree that if you work in R, people should probably use ggplot2, but it might be nice to write to ggplot2 for a few reasons:
- If you want the plot declaration to match across languages. (i.e. you work in R, but collaborator works in SQL, you use ggsql as lingua franca)
- You want to tweak plots with ggplot2 exclusive functionality, such as that provided by the extension ecosystem.
- You want the database backend to avoid materialising data for summaries (and are unfamiliar with dbplyr).
4. In the far future, archeologists will excavate GitHub's arctic vault on the Svalbart islands and find ggsql as the Rosetta's stone of GoG plotting syntax.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by reviewing the repository structure and current plotting or writer architecture, then define the scope of ggplot2 output and its relationship to the SQL backend. Done requires an agreed design, implementation criteria, and tests for the proposed writer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, rust, sql
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100