Problem/Motivation

Our schema is going quickly and so are our resolver definitions. To make sure we don't make mistakes, having an overview of orphaned and missing resolvers makes sure we can easily figure out whether we need to adjust the schema or can clean up resolver definitions.

Steps to reproduce

Proposed resolution

Implement a social_graphql_devel module that can provide such an overview for GraphQL servers.

Remaining tasks

User interface changes

API changes

Data model changes

Comments

Kingdutch created an issue. See original summary.

kingdutch’s picture

kingdutch
he/him
Primary language English
commented
Status: Active » Needs review
Parent issue: » #3174541: [Meta] GraphQL Support in Open Social

https://github.com/goalgorilla/open_social/pull/2194

kingdutch’s picture

kingdutch
he/him
Primary language English
commented
Status: Needs review » Fixed
kingdutch’s picture

kingdutch
he/him
Primary language English
commented
Status: Fixed » Needs review

re-opened since this will be moved to the graphql module itself, now tracked in https://github.com/goalgorilla/open_social/pull/2207

Blocked until the next release from the graphql module, then our PR can be merged once tests pass with the updated module.

  • 727cfc8 committed on 10.0.x 
    Issue #3194938 by Kingdutch: [GraphQL] As a developer I want insight...
kingdutch’s picture

kingdutch
he/him
Primary language English
commented
Version: 8.x-9.x-dev » 10.2.x-dev
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.