Skip to content

Conversation

yclkvnc
Copy link
Contributor

@yclkvnc yclkvnc commented Jul 21, 2023

Closes #5169

Hi @roji, I've opened the issue (#5169) with my 2nd account, but opening the PR with my main account. I have a couple of questions:

  • I've added the nullable CultureInfo to the constructor as you proposed and gave it a default value null. It will still be a breaking change but at least you can use it as before. Is it ok?
  • I've added a CultureInfo parameter to the existing TestCases and set it to null for existing cases and added spesific cases to the end of the list. I can seperate them to another TestCases list in another file if you want

@yclkvnc yclkvnc requested review from roji and vonzshik as code owners July 21, 2023 20:39
@yclkvnc yclkvnc changed the title 5169 snakecasenametranslator invariantculture Change NpgsqlSnakeCaseNameTranslator to use InvariantCulture by default, accept culture parameter Jul 21, 2023
Copy link
Member

@roji roji left a comment

Choose a reason for hiding this comment

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

LGTM, thanks @yclkvnc!

Yeah, the constructor change is a binary-breaking change, but not a source-breaking one; that's only really important if a 3rd-party library uses the older constructor - it's hard for me to imagine such a scenario. If we get a complaint we can always split the constructor into two to maintain backwards compat.

And thanks for the testing too!

@roji roji merged commit 83aecda into npgsql:main Jul 22, 2023
@yclkvnc
Copy link
Contributor Author

yclkvnc commented Jul 22, 2023

You're welcome and thank you :)

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.

Change NpgsqlSnakeCaseNameTranslator to use InvariantCulture by default, accept culture parameter
2 participants