WIP: Add a .shiny
submodule (do not merge)
#77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Here's the basic start on adding the
.shiny
submodule. Locally, I've created a little app similar (but better) to the one I posted in Discord.There's still a lot to do (namely tests and docs). The basic premise of the approach is this:
GT
output into a shiny apppb.Validate
object. Wepointblank
will call.interogate()
on itGT
instance to preview the data the way the user might want. If this isn't provided, we build a simple one ourselves:I've included a brief app that demonstrates usage.
Questions
server: shiny
work with the doc builds? More to the point, how would you like this documented?Related GitHub Issues and PRs
None. Working based on this:
https://discord.com/channels/1345877328982446110/1346204992226197627/1346257619396067400
Checklist
.qmd
example show casing the module's usageExample App
Click to see app source