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

Added StringComparison to StringAssert Contains(), EndsWith() & StartsWith() #691

Merged
merged 7 commits into from
Sep 29, 2020
Merged

Added StringComparison to StringAssert Contains(), EndsWith() & StartsWith() #691

merged 7 commits into from
Sep 29, 2020

Conversation

HeroMaxPower
Copy link
Contributor

@HeroMaxPower HeroMaxPower commented Feb 27, 2020

Description:

Added StringComparison to StringAssert Contains, EndsWith & StartsWith
Added tests to test functionality
Added API comment on StringComparison Enum
Updated APIs to default to StringComparison.Ordinal

Probably needs API documentation updates if this gets merged.

Resolves #154

@HeroMaxPower HeroMaxPower changed the title Added StringComparison to StringAssert Contains, EndsWith & StartsWith Added StringComparison to StringAssert Contains(), EndsWith() & StartsWith() Feb 28, 2020
Copy link

@304NotModified 304NotModified left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(I guess unintended) breaking change

@nohwnd
Copy link
Member

nohwnd commented Jun 16, 2020

@HeroMaxPower are you going to address the PR comments or should I?

@HeroMaxPower
Copy link
Contributor Author

Yes please, i haven't had time in my personal life to look at these. 👍

@nohwnd
Copy link
Member

nohwnd commented Jun 17, 2020

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@nohwnd
Copy link
Member

nohwnd commented Jun 18, 2020

@304NotModified Would you review again please? I had to pass empty array to disambiguate the calls (before we passed null). The compiler will pass empty array for us, so we should not be doing anything wrong. Unless the user passed StringComparison as the actual first param, then they now would get different overload than before. But that is unlikely scenario.

@HeroMaxPower
Copy link
Contributor Author

@304NotModified any updates?

Copy link

@304NotModified 304NotModified left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! Thanks for the reminder!

@HeroMaxPower
Copy link
Contributor Author

@nohwnd i think this is ready to be merged 👍

@nohwnd
Copy link
Member

nohwnd commented Sep 29, 2020

@Haplois could you review and merge please?

@Haplois Haplois self-assigned this Sep 29, 2020
@Haplois Haplois merged commit ec18af6 into microsoft:master Sep 29, 2020
@HeroMaxPower HeroMaxPower deleted the string-asserts-with-string-comparison-options branch September 29, 2020 09:58
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.

StringAssert APIs do not have ignorecase overloads
4 participants