Process input tables simplification #2143
Merged
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.
A small PR setting some of the foundations to do analysis of blocking rule without a linker.
This is a step towards solving #2142
Since the
process_input_tables
function is used only during table registration (and is part of the table registration logic) it makes senes to perform is as part of table registration as opposed to a separate function call.This means that e.g. in
profile_columns
we need a singleregister_multiple_tables
call rather than three lines:We'll need similar logic for any functions that do exploratory analysis without a linker, so we don't want to have to repeatedly write this logic.
Don't know why the docs build triggered here, but all the other tests are passing