Support iterative glue-ing#30
Draft
allenbaron wants to merge 5 commits into
Draft
Conversation
glue::glue() and glueV() identify expression string(s) as unnamed inputs and temporary variables as named inputs. This drops the requirement for explicitly stating the order of expression strings using numbers as names for expression strings, which is likely not intuitive, and makes inputs consistent with other glue functions. It also adds the .sep argument.
Tests: PASS
Instead of silently returning an empty glue object like glue::glue() and glueV(), glueV_cum() will produce an error when no expression string is provided as input. This has been a common source of mistakes when using glue::glue(). Tests: PASS
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This creates
glueV_cum()which performs iterative glue-ing, using the same wrappers asglueV()in this package (i.e.!<<&>>!). It was designed to support iterative SPARQL query building.One option for data removal, and perhaps other implementations via the Google Sheet curation schema, is to build the appropriate SPARQL queries to remove specific data via jinja-like templating (
glue-ing). Depending on how this is done, it might require iterative SPARQL query building.Note
The security implications of iterative
glue-ing are unclear.