Fix: duplicate column selection issue in getMany with joins and pagination #34
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 pull request proposes a fix for the duplicate column names encountered when using getMany with joins and pagination in NestJS CRUD nestjsx#788.
The current solution in nestjsx#788 excludes the "id" column, which might not be ideal for all relational scenarios. This pull request aims to address duplication directly within the column array, preserving the "id" column when necessary or any duplicated column.
Key points:
Please review and provide feedback on the proposed approach.
issue #32