Repository navigation
feat(sdk): deprecate the postOtlp and maybeGzip exports - #199
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
postOtlpandmaybeGzipare public exports of@telemetry-dev/otel, but nothing outside the package uses them:postOtlphas no caller at all, andmaybeGzipis only a step of the exporters. Both are now marked@deprecated, so editors flag them, and they can be dropped in a future breaking release. They keep working with the same signatures until then.postOtlppoints tocreateTraceExporter,createLogExporterandcreateMetricExporterinstead. The exporters now call a privategzipLargeBody, andmaybeGzipis an alias of it, so the package itself doesn't call a deprecated name and removing the export later is a one-line change. The builtindex.d.mtscarries both@deprecatedtags.Refs #83