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
type User struct {
ID string `description:"user id"`
}
We do
type User struct {
// user id
ID string
}
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.
Currently, to provide descriptions for fields we need to use the
descriptionstruct 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
enumsand type definitions. We should continue to support thedescriptionstruct tag as an override in case the user wants to use different descriptions on the GraphQL and Go sides.