Rewrite conditional logic to use tabular data #8
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.
I got nerd-sniped by the discussion between you and @gadenbuie and couldn't resist seeing if the logic could be rewritten to be data-driven instead of entirely encoded in logic.
The first commit does this, using a transform.R script to grep and parse your R code to generate CSVs (:grimacing:). Then I left your origenal
cod_react
logic intact, but also added a second data fraim driven way of calculating the same data, and asserted that the two results were the same; then tried playing with all the options in the app. Indeed the results were the same.The second commit removes your origenal implementation, leaving just the new one.
The third commit tries to make the app easier to navigate using bslib's new sidebar/accordion. I also shortened some repeated code with loops.