We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fetchApi
The auto-generated JS API client doesn't support a custom fetchApi for the @hirosystems/token-metadata-api-client, as it does with the other APIs.
@hirosystems/token-metadata-api-client
e.g.
// node_modules/@hirosystems/token-metadata-api-client/dist/configuration.d.ts export interface ConfigurationParameters { apiKey?: string | ((name: string) => string); username?: string; password?: string; accessToken?: string | ((name: string, scopes?: string[]) => string); basePath?: string; }
vs other packages in @stacks/blockchain-api-client which do support the fetchApi argument in their Configuration.
@stacks/blockchain-api-client
Configuration
Being unable to override the fetch function prohibits clients from being able to monitor and modify requests, e.g. to add API key headers etc.
The text was updated successfully, but these errors were encountered:
🎉 This issue has been resolved in version 1.1.6 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
The auto-generated JS API client doesn't support a custom
fetchApi
for the@hirosystems/token-metadata-api-client
, as it does with the other APIs.e.g.
vs other packages in
@stacks/blockchain-api-client
which do support thefetchApi
argument in theirConfiguration
.Being unable to override the fetch function prohibits clients from being able to monitor and modify requests, e.g. to add API key headers etc.
The text was updated successfully, but these errors were encountered: