You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need to use both octokit.net and octokit.graphql.net in the same project and I wish I could more easily share authorization tokens between both SDKs. I've written an ICredentialStore to cache and refresh authorization tokens, but this interface is slightly different between octokit.net and octokit.graphql.net, which complicates the implementation unnecessarily.
It's a pretty minor issue, but I wish these two packages worked together more seamlessly. One possible solution would be to extract authorization related code into a separate package that both projects could depend on. Such a change might also help address #128
The text was updated successfully, but these errors were encountered:
This is one of the future design changes we hope to make as we begin leaning into generative SDKs - we'd like to abstract things such as models, auth, caching, throttling, and the like, which could easily be referenced in, as you suggest. We've got a little ways to go to get things moving in that direction, but until then, please join the discussion here and here - we'd love to have your voice and thoughts woven into the future of what this might all look like in the future.
I need to use both octokit.net and octokit.graphql.net in the same project and I wish I could more easily share authorization tokens between both SDKs. I've written an
ICredentialStore
to cache and refresh authorization tokens, but this interface is slightly different between octokit.net and octokit.graphql.net, which complicates the implementation unnecessarily.It's a pretty minor issue, but I wish these two packages worked together more seamlessly. One possible solution would be to extract authorization related code into a separate package that both projects could depend on. Such a change might also help address #128
The text was updated successfully, but these errors were encountered: