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.
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Deduce model field names from custom prefetches #473
base: main
Are you sure you want to change the base?
Deduce model field names from custom prefetches #473
Changes from 4 commits
77a44d6
0088e39
f82d3f9
0b2d41d
16ff873
6d4889d
d46a2d3
6f64194
e25be2d
92cdc12
79ce913
746ec95
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check failure on line 199 in strawberry_django/optimizer.py
GitHub Actions / Typing
Check failure on line 472 in strawberry_django/optimizer.py
GitHub Actions / Typing
Check failure on line 524 in strawberry_django/optimizer.py
GitHub Actions / Typing
Check failure on line 524 in strawberry_django/optimizer.py
GitHub Actions / Typing
Check failure on line 567 in strawberry_django/optimizer.py
GitHub Actions / Typing
Check failure on line 577 in strawberry_django/optimizer.py
GitHub Actions / Typing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion (llm): This block introduces a significant change in how prefetches are handled based on the presence of
custom_prefetches
. It's a complex addition that could benefit from a bit more inline documentation to explain the rationale behind this approach, especially for future maintainers.Check warning on line 639 in strawberry_django/optimizer.py
GitHub Actions / Typing
Check failure on line 647 in strawberry_django/optimizer.py
GitHub Actions / Typing
Check failure on line 1 in tests/projects/models.py
GitHub Actions / Typing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a left over from a test attempt? =P
This is not being used, so it should be removed
Check failure on line 563 in tests/test_optimizer.py
GitHub Actions / Typing
Check failure on line 608 in tests/test_optimizer.py
GitHub Actions / Typing