Skip to content

Fix reverse o2o relation resolution #664

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.

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

Closed
wants to merge 1 commit into from

Conversation

mvanlonden
Copy link
Member

@mvanlonden mvanlonden commented Jun 9, 2019

Fixes #662
Supersedes #663

@robertpro used your fix and added some tests so we won't see this regression again

@robertpro
Copy link
Contributor

@mvanlonden Thanks!, I am still learning graphene, next time I will add tests!

@coveralls
Copy link

Coverage Status

Coverage remained the same at 92.718% when pulling 4dc4d9a on mvanlonden:o2o-relation into bad8e13 on graphql-python:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 92.718% when pulling 4dc4d9a on mvanlonden:o2o-relation into bad8e13 on graphql-python:master.

@mvanlonden
Copy link
Member Author

Added tests to @robertpro 's PR

@mvanlonden mvanlonden closed this Jun 9, 2019
@mvanlonden mvanlonden deleted the o2o-relation branch June 9, 2019 19:42
@robertpro
Copy link
Contributor

@mvanlonden you closed this PR instead of merge?

@mvanlonden
Copy link
Member Author

Yes I wanted to keep your contribution so I just added my tests to the PR you started @robertpro

@robertpro
Copy link
Contributor

Nice, thanks again @mvanlonden

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

OneToOne Relations stop working on 2.3.0
3 participants