fix: handle overlapping property / database names in querybuilder #7042
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
we should always prioritize replacement of any property path first, then property names, then database names, then relation values whenever there's ambiguous values fixes typeorm#7030
|
Yeah. this fixed my issue. |
edcolvin
pushed a commit
to edcolvin/typeorm
that referenced
this pull request
Nov 12, 2020
…peorm#7042) we should always prioritize replacement of any property path first, then property names, then database names, then relation values whenever there's ambiguous values fixes typeorm#7030
nebkat
pushed a commit
to nebkat/typeorm
that referenced
this pull request
Jan 9, 2021
…peorm#7042) we should always prioritize replacement of any property path first, then property names, then database names, then relation values whenever there's ambiguous values fixes typeorm#7030
nebkat
pushed a commit
to nebkat/typeorm
that referenced
this pull request
Jan 9, 2021
…peorm#7042) we should always prioritize replacement of any property path first, then property names, then database names, then relation values whenever there's ambiguous values fixes typeorm#7030
zaro
pushed a commit
to zaro/typeorm
that referenced
this pull request
Jan 12, 2021
…peorm#7042) we should always prioritize replacement of any property path first, then property names, then database names, then relation values whenever there's ambiguous values fixes typeorm#7030
This was referenced Mar 15, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of change
we should always prioritize replacement of any property path first,
then property names, then database names, then relation values
whenever there's ambiguous values
fixes #7030
Pull-Request Checklist
masterbranchnpm run lintpasses with this changenpm run testpasses with this changeFixes #0000