Improve min_cost_string_conversion with validation, case-insensitive option, and more tests #12886
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.
This PR enhances the min_cost_string_conversion.py algorithm by adding input validation, case-insensitive mode, additional doctests, and improved CLI usability while preserving backward compatibility and passing all existing tests.
Describe your change:
I made a few enhancements to the min_cost_string_conversion module:
Added checks to handle invalid input more gracefully.
Introduced an ignore_case option for case-insensitive string comparisons.
Added more doctests to cover edge cases, single-character changes, and mixed-case scenarios.
Cleaned up comments to make the code easier to follow.
before:
after:
*
Add an algorithm?
[ * ] Fix a bug or typo in an existing algorithm?
[ * ] Add or change doctests? -- Note: Please avoid changing both code and tests in a single pull request.
Documentation change?
Checklist: