feat: Add is_column_selection()
to expression meta, enhance expand_selector
#16479
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.
Closes #16448.
Extends the existing expression meta/introspection methods with a new one that determines if a given expression exclusively selects columns. This includes selectors, bare/multi
col
, regexcol
, dtypecol
, use ofexclude
, and the positional top-level functions (first/last/nth). Aliased column selections are optionally allowed, but not by default.This allows
expand_selector
to offer a new "strict=False" option such that it can additionally expand expressions likecs.starts_with("x").exclude("x!!")
, which would previously raise an error.Should cover the Great Tables use-case in the linked issue (@machow).
(Also: fixed some versionadded/changed tags as a trivial drive-by).
Example
New
meta
method accurately identifies all of the below:Enhanced
expand_selector
:Before
After