Skip to content

Add best practice about robust applications#2434

Merged
leebyron merged 4 commits into
sourcefrom
robust-clients
Jul 2, 2026
Merged

Add best practice about robust applications#2434
leebyron merged 4 commits into
sourcefrom
robust-clients

Conversation

@martinbonnin

@martinbonnin martinbonnin commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Robust applications must:

  • Plan for unknown enum values
  • Plan for unknown union types being added
  • Not force unwrap nullable types

@vercel

vercel Bot commented Jun 16, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
graphql-github-io Ready Ready Preview, Comment Jun 16, 2026 11:06am

Request Review

@martinbonnin martinbonnin changed the title Add best practice about robust clients Add best practice about robust applications Jun 16, 2026
}
```

In typed languages, if your codegen tool marks enums as exhaustive, configure it to generate a catch-all variant (often called `UNKNOWN` or `%future added value`) so the compiler enforces that you handle it.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So - we should have an admonition here.. as %future added value is fake in some clients

@mjmahone mjmahone left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great!

@leebyron leebyron merged commit 023d132 into source Jul 2, 2026
6 checks passed
@leebyron leebyron deleted the robust-clients branch July 2, 2026 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants