octokit.graphql.net icon indicating copy to clipboard operation
octokit.graphql.net copied to clipboard

Published 20 hours ago • verified publisher icon octokit

Build a proper solution to handle preview headers

Open StanleyGoldman opened this issue 7 years ago • 2 comments

We are allowing #127, but we need to give more thought to properly handling preview headers. This is not the first and won't be the last

StanleyGoldman avatar Jul 18 '18 15:07 StanleyGoldman

This is apart from the header issue, but I was thinking: what if we could implement preview APIs as extension methods? That way you'd need to do a e.g. using Octokit.GraphQL.Preview.Antilope to import the preview API into scope. That way we'd separate the preview APIs from stable, meaning users would have to explicitly opt-in.

Moving onto the headers, maybe we could then detect which preview APIs are in use and enable them?

Disclaimer: These are just ideas, I've not really thought about implementation ;)

grokys avatar Jul 19 '18 20:07 grokys