-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
Tweak to improve DX for newcomers (re-exported strawberry type) #462
Comments
Hrm, I get what you mean here from a new user perspective, specially for someone new to strawberry that usually don't know that I somewhat like this proposal, but I'm not totally sure it brings value enough instead of improving the documentation and ensuring the user knows the difference between What do you think about this @patrick91 ? |
I'm -1 for this 😊 A GraphQL Query type is a standard type, what makes it special is it being set on |
OK, so -2 on renaming the decorator. We could elaborate in the docs that Could it work to simply use |
I do agree that Maybe we could acomplish this by adding docs on
We would need to change |
Feature Request Type
Description
When I was working with the documentation improvements the other week, one area where I realised I was struggling was the difference between
@strawberry.type
and@strawberry_django.type
.See my comments in the code below (extracted from that featured in the docs):
Proposed Solution
What about, within
strawberry-django
, we do:Then the last section of the code above looks like:
I think this solution has the following benefits:
strawberry_django
to avoid digging immediately into the much bigger and more complex strawberry docsEffort required
Less than an hour. I'm happy to make this PR myself and update documentation to match if my suggestion has the blessing of the maintainers, no breaking changes required.
Upvote & Fund
The text was updated successfully, but these errors were encountered: