Skip to content

added ordering rationale: #158

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

Merged
merged 2 commits into from
Aug 23, 2018
Merged

added ordering rationale: #158

merged 2 commits into from
Aug 23, 2018

Conversation

SergeyKanzhelev
Copy link
Member

I suggest to close #123 with the words about ordering in rationale document. #123 refers to other two issues which are tracked separately already

@@ -31,6 +31,22 @@ interfere with identification of the tracing system responsible for an entry.
- The typical name will be a single word in latin and the value will be a
copy of the `traceparent` format or an opaque string.

## Ordering of keys in `tracestate`

Specification calls for ordering of values in tracestate. This requirements allows better interoperability between tracing vendors.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this md file uses different line size based on whoever updates it. Probably makes sense to format the entire file using some rules. Maybe in a different PR. But at least in this PR use consistent line sizes please.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed this as well. I wonder if there is a setting common between vim and vscode that will control it. I'll configure this for vscode.

@SergeyKanzhelev SergeyKanzhelev merged commit 40c81ec into master Aug 23, 2018
@SergeyKanzhelev SergeyKanzhelev deleted the sergkanz/ordering branch August 23, 2018 23:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Structure of TraceState
2 participants