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
For new/experimental functionality, the GitHub API requires the submission of an additional header to enable features (see, for example, the API documentation note below related to the new Topics attributes):
Currently while the HTTP mechanisms are well-factored, they are only plugable via changes to the source code of this library. To ease extensibility (and meet the needs of additional headers), please consider either:
Implementing a Factory-style improvement that would allow for us to provide a Requester that could, for examlpe include the headers within the implementation of buildRequest, or
Provide a pathway for injecting headers into the Requester's headers property, possibly via a static-level "DefaultHeaders" that is publicly available.
The text was updated successfully, but these errors were encountered:
I don't understand the motivation for this. This library has no "extensibility" in the sense of defining additional API (like "topics" in your example) outside. The only way to do so is to change the source code of this library.
For new/experimental functionality, the GitHub API requires the submission of an additional header to enable features (see, for example, the API documentation note below related to the new Topics attributes):
Currently while the HTTP mechanisms are well-factored, they are only plugable via changes to the source code of this library. To ease extensibility (and meet the needs of additional headers), please consider either:
Requester
that could, for examlpe include the headers within the implementation ofbuildRequest
, orRequester
'sheaders
property, possibly via a static-level "DefaultHeaders" that is publicly available.The text was updated successfully, but these errors were encountered: