Added type_insensitive parameter for equals_string_part operator

[aniemes]

No description provided.

[github-actions]

Updated schema has not been merged with markdown descriptions. Please run the "Merge Schema with Markdown Descriptions" workflow to update the merged schema files.

[RamilCDISC]

The PR looks great to me. I will recommend minor updates to the tests for covering the edge cases of

1. No regex match
2. Empty string/null target
3. Case for deos_not_equal_string_part False
4. Test for leading zero behavior.

[aniemes]

Hi Ramil,
Thank you for reviewing it! I will work on the changes now to cover the edge cases and update the Operator.md file as you said above.
Thanks!
Adam

[aniemes]

@RamilCDISC
So I am having some trouble with the 'no regex' as this seems to be expected. I added this into a new test case:
if operator == "equals_string_part": result = dataframe_type.equals_string_part( { "target": "target", "comparator": comparator, "regex": "(.*)", "type_insensitive": True, } )

But this is still using regex. Can you suggest how to test this without using regex? I am also have trouble with the empty string/null targets.

I tried this:
( {"VAR2": ["", ""], "target": [0, 0]}, "VAR2", "equals_string_part", PandasDataset, [True, True], )
And an empty target array but neither worked.

Pasted test file for reference.

test_string_comparison.py

[RamilCDISC]

My intention with 'no regex match' was to ask for a test where the regex does not return any match, not to test without a regex. I see that my comment was not very clear. The edge cases I requested is to have a case where the passed regex does not return any match. Passing a regex is required.

For the null/empty target case, your example has empty values in VAR2 not in the target. target is '[0,0]'. I would test it with explicit empty/null values in target columns.