Skip to content

fix wrong resolver._m2m if related_query_name is set on m2m fields #173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix wrong resolver._m2m if related_query_name is set on m2m fields #173

wants to merge 1 commit into from

Conversation

AlbertoNieto44
Copy link

@AlbertoNieto44 AlbertoNieto44 commented Jun 17, 2025 •
edited
Loading

Fixes #172

@AlbertoNieto44
Copy link
Author

AlbertoNieto44 commented Jun 17, 2025 •
edited
Loading

@jerch Here you are :)

@coveralls
Copy link

Pull Request Test Coverage Report for Build 15699355721

Details

  • 4 of 4 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 94.858%
Totals Coverage Status
Change from base Build 14884527532: 0.0%
Covered Lines: 1134
Relevant Lines: 1180
💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Wrong resolver._m2m computation for m2m relations if related_query_name is set
2 participants
@AlbertoNieto44 @coveralls