fix: api client should set default telemetry if not specified #160
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ensure that a default telemetry instance is created when creating an API client directly.
Description
When a
Configuration
is created viaNewConfiguration
, we ensure that a default telemetry is created if not specified. However, when creating aConfiguration
directly as shown in #466, no telemetry is created. This causestelemetry.Get
to create a new telemetry instance on each call (e.g., each API call), which causes the map to grow unbounded.This change ensures that a default Telemetry instance is created when creating a new
APIClient
.References
openfga/sdk-generator#466
Review Checklist
main