Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes issue #1917 not contains filter #1953

Merged
merged 2 commits into from
Jan 8, 2023

Conversation

cjundt
Copy link
Contributor

@cjundt cjundt commented Jan 5, 2023

Added unit tests and code fix in order to handle the "Not" string filters family as expected.

cjundt and others added 2 commits January 9, 2023 00:14
…n just pass a value and get info, if the value satisfies the filter or not. Having two different semantic for condition makes it hard to reason about the code.
@jahav jahav added this to the v0.100 milestone Jan 8, 2023
@jahav jahav merged commit 95a50e2 into ClosedXML:develop Jan 8, 2023
@jahav
Copy link
Member

jahav commented Jan 8, 2023

Resolves #1917

@jahav
Copy link
Member

jahav commented Jan 8, 2023

@cjundt I didn't like how the condition has sometimes had to be inverted, so I changed to code so it always returns true when value satisfies the filter.

Be warned that autofilter is going to be revamped, likely in 0.101, I already researched how it actually work and done some work, but it just didn't make it. You have seen it, conditions are duplicated across load code, XLFilteredColumn and XLCustomFilteredColumn, filters don't work correctly (no wildcard support, no correct coercion for comparison filters, equals operator applying filter on filter value, while not equal uses normal textual value and the rest).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants