Khan/genqlient

Expand the flatten option to support fields

Open

#30 opened on Apr 22, 2021

View on GitHub
 (3 comments) (0 reactions) (1 assignee)Go (141 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (1,310 stars)
PR merge metrics
 (PR metrics pending)

Description

If you do mutation { MyMutation { error { code } } }, or something, we should be able to just return (code string, err error), at least if you ask us too. This would be a nice convenience -- the helper's callers no longer have to know as much about the query structure -- but the rules and logic to do it are surprisingly subtle.

Contributor guide

Research direction
Investigate the current flatten option implementation and determine how to extend it to allow returning fields directly from mutation responses, like (code string, err error), considering the subtle rules for mapping response data.
Tech stack
go
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GoGraphQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50