Document explicit prefix/suffix separators #216
Merged
Conversation
This file contains 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
No separator is added, so it should be included in the given string to separate the prefix/suffix from the rest of the metric name.
|
Sorry for the delay in review, and thanks for the info on this! |
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.
This adds documentation for the
prefixandsuffixconfigs.No separator (e.g.
.) is added, so it should be included in the given string to separate the prefix/suffix from the rest of the metric name. See #215 for more context.I tried implementing auto-separating prefixes and suffixes, but it turns out to be a little complex to keep the option for the old behaviour. This at least clarifies the existing behaviour, until such as time as it is decided to change it.