Fixing onConflict case when custom NamingStrategy is used #3238
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.
Fixes #3144
Notes
Apologies for the messy tests. The newly added test fails when used with ]querySchema], even before the changes introduced in #3137. I’m not very familiar with this feature, so it’s possible that not renaming fields when using
querySchemais the expected behavioгr.BTW suggested
sbt scalariformFormat test:scalariformFormatdoesn't seem to work and printssbt scalafmtworked fine though@getquill/maintainers