-
Notifications
You must be signed in to change notification settings - Fork 893
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove LabelSet #560
Remove LabelSet #560
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The api-user.md
file is so old that I had to stop looking carefully. I'd like to get this in quickly and continue editing the metrics API spec in future PRs. Thanks!
Thanks for the quick reviews, hopefully this change is still worth making even if the whole file will be overhauled soon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR includes a lot of changes where unrelated line breaks were moved to different positions which makes it hard to spot where content was actually altered or just moved to another line. Please try to avoid this to make reviewing easier. Thanks!
We actually settled for soft breaks a while ago (#192 (comment)) but I also usually keep the style already in place in existing documents.
Re: line-breaks |
Co-Authored-By: Armin Ruech <[email protected]>
Sorry about the line breaks @arminru, I re-wrapped paragraphs I edited which made for a lot of spurious line diffs.
I'd be happy to, I'll put up a PR. |
May we merge this ahead of adding soft-breaks everywhere? |
* Scrub LabelSet references * Update metrics API TOC * Remove more references to "label sets" * Lint * Update go examples for @jmacd's comments * Update specification/metrics/api-user.md Co-Authored-By: Armin Ruech <[email protected]> Co-authored-by: Armin Ruech <[email protected]> Co-authored-by: Bogdan Drutu <[email protected]>
Following open-telemetry/oteps#90.
@jmacd please check my work here, I may have mangled some of your go examples.