make every conversation's calculations reproducible to the app author
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44
- Forks
- 1
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 142
Description
Halfway there would be inlining the database connection code and then interleaving run_sql() calls as dbExecute() and run_r() as normal R code in a .R file.
The proper treatment might use ir based on the active connect deployment and intelligently resolve viewer-based credentials. That still doesn't account for changes in the queried database, though.
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 or tests are named. Start by reviewing the proposed run_sql()/dbExecute() and run_r() flow, then read the linked ir material and investigate active Connect deployments and viewer-based credentials. The issue is done only after the project agrees on a reproducibility design that also addresses changes in the queried database.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, sql
- Domain
- data, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100