Revert "Allow future addition of Histogram MinMax via View" #2706
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.
Reverts #2705
We want to avoid the situation where a user can add a statement such as:
.AddView(instrumentName: "MyCounter", new HistogramConfiguration() { Name = "newname"})This will not update the
Counterto aHistogramSince this will not be a breaking change if added after
1.2.0release, we can add it later.Documentation on types of breaking changes: https://docs.microsoft.com/en-us/dotnet/core/compatibility/#types
I also manually ran the APICompat tool to ensure that this will not be a breaking change if we decide to add it later on.