You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, to provide descriptions for fields we need to use the description struct tag. While this is fine, the lines would be really long for long descriptions, and it might be easier to use regular docstrings for descriptions.
Using docstrings would also allow us to support descriptions for enums and type definitions. We should continue to support the description struct tag as an override in case the user wants to use different descriptions on the GraphQL and Go sides.
The text was updated successfully, but these errors were encountered:
Currently, to provide descriptions for fields we need to use the
description
struct tag. While this is fine, the lines would be really long for long descriptions, and it might be easier to use regular docstrings for descriptions.Instead of
We do
Using docstrings would also allow us to support descriptions for
enums
and type definitions. We should continue to support thedescription
struct tag as an override in case the user wants to use different descriptions on the GraphQL and Go sides.The text was updated successfully, but these errors were encountered: