Display better genqclient graphql errors

Open
#1,272 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go, graphql
Domain
api, cli

Research direction

Start by reading the linked genqclient documentation on error handling, then locate how flyctl receives and formats those GraphQL errors. Clarify the desired output and verify that genqclient errors are displayed more usefully when the change is complete.

Written by the indexing model from the issue text.

Description

ux-annoying

The formatting of errors coming from genqclient. Should be fixed. Here's some info about how errors are handled from genqclient:

https://github.com/Khan/genqlient/blob/main/docs/client_config.md#handling-errors

Dominant language
Go
Stars
1.7k
Forks
311
Avg merge
12h 50m
Merged PRs (30d)
78

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from superfly/flyctl

All issues in superfly/flyctl

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.