[draft] feat(sdk-metrics)!: use factory functions over classes #4932
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.
DRAFT: shows how it could look like if we'd use factory functions over class constructors. Currently types of private properties end up being part of the public interface, which causes breaking changes left, right and center. Using a factory function we can only expose what we want the user to use, this enables us to make larger changes to SDK internals without breaking users.
Note: This is combined with #4931 as it also eliminates some classes that we previously exported.
Old:
New:
For a user it's actually a fairly minimal change but for us it means that we can freely modify the SDK's MeterProvider and all previously unintentionally public referenced and transitively referenced types.