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.
PR Checklist
Description
Review Notes
I haven't linked to example sheets as I couldn't remember if we have good examples of data generators or not
Author Notes
I don't think the example outlined has ever been coded into a debug/example template for the debug repo - might be useful to do so for easier reference
Dev Notes
The Special Case issue mentioned in the docs is particular to the case where the generator is used to create data_pipes, which in turn need to refer to
@row
variables. The@row
is processed one level too soon (i.e. processed by the generator and not left for processing within the data_pipe).I couldn't wrap my head around how best to go about making sure something like that doesn't happen in the code (felt like a lot of potential for knock-ons if too heavy-handed and hacky if writing single-level exceptions), so for now hopefully just having documented is sufficient (assume a pretty rare case)
Git Issues
Closes #
Screenshots/Videos
Rendered Doc