Skip to content

Missing LOC in django model form documentation (fixes #602)#605

Merged
mvanlonden merged 1 commit intographql-python:masterfrom
GitRon:bugfix/missing-type-declaration-in-docs
Apr 27, 2019
Merged

Missing LOC in django model form documentation (fixes #602)#605
mvanlonden merged 1 commit intographql-python:masterfrom
GitRon:bugfix/missing-type-declaration-in-docs

Conversation

@GitRon
Copy link
Copy Markdown
Contributor

@GitRon GitRon commented Mar 27, 2019

If you don't put this in your code you'll end up with an import error deep in the source code. Took me about 6h work to figure this out 🙈

@zbyte64
Copy link
Copy Markdown
Collaborator

zbyte64 commented Mar 27, 2019

I think PetMutation is suppose to have field name and not pet. What is not shown in the documentation is how to include the PetMutation in the root Mutation class, the LOC here is probably also valid but I don't think it is idiomatic.

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 94.356% when pulling 547a4cb on GitRon:bugfix/missing-type-declaration-in-docs into ea2cd98 on graphql-python:master.

4 similar comments
@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 94.356% when pulling 547a4cb on GitRon:bugfix/missing-type-declaration-in-docs into ea2cd98 on graphql-python:master.

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 94.356% when pulling 547a4cb on GitRon:bugfix/missing-type-declaration-in-docs into ea2cd98 on graphql-python:master.

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 94.356% when pulling 547a4cb on GitRon:bugfix/missing-type-declaration-in-docs into ea2cd98 on graphql-python:master.

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 94.356% when pulling 547a4cb on GitRon:bugfix/missing-type-declaration-in-docs into ea2cd98 on graphql-python:master.

@GitRon
Copy link
Copy Markdown
Contributor Author

GitRon commented Mar 28, 2019

As I said if you don't put this line you get a vague import error. I really think that this needs to be documented!

@GitRon
Copy link
Copy Markdown
Contributor Author

GitRon commented Apr 15, 2019

After giving it a second thought I really would be happy if we did not need this line at all. So maybe there is another bug in the background? I did not manage to find out where the problem comes from...

Copy link
Copy Markdown
Member

@mvanlonden mvanlonden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This part of the docs is labeled as experimental so even if this isn't the most idiomatic approach it will save others some headache. Can revisit at a later time with a more idiomatic approach or make this field definition obsolete.

@mvanlonden mvanlonden merged commit 2016011 into graphql-python:master Apr 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants