You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the filter_by_text_contains or filter_by_text_equals, it would be nice to be able to have a parameter ignore_case which allows for caseless matching.
For example, currently filtering by "CONTENT" and "Content" returns two different sets of elements.
When processing less uniform PDFs, hard-coding the correct case is difficult (most commonly, such headers are either in sentence case or all-caps), and currently the workaround I am using is to chain together or logic with multiple versions of the string:
But this seems like a much more inefficient way of going about it than being able to directly access the element texts and using casefold() to match them.
The text was updated successfully, but these errors were encountered:
Feature Request
When using the
filter_by_text_contains
orfilter_by_text_equals
, it would be nice to be able to have a parameterignore_case
which allows for caseless matching.For example, currently filtering by "CONTENT" and "Content" returns two different sets of elements.
When processing less uniform PDFs, hard-coding the correct case is difficult (most commonly, such headers are either in sentence case or all-caps), and currently the workaround I am using is to chain together
or
logic with multiple versions of the string:But this seems like a much more inefficient way of going about it than being able to directly access the element texts and using
casefold()
to match them.The text was updated successfully, but these errors were encountered: