Adds a pure javascript implementation of trace contexts #571
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
|
maraisr marked as non substantive for IPR from ash-nazg. |
basti1302
approved these changes
Apr 8, 2024
kalyanaj
approved these changes
Apr 8, 2024
SergeyKanzhelev
approved these changes
Oct 8, 2024
dyladan
approved these changes
Oct 8, 2024
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.
Ive built and published an NPM (and soon deno, jsr) library for dealing with trace contexts. Was originally built as a backing plane for my tracer rian, but think this can be useful for many more people.
I am also running your test harness level 2:
w3c validation test ✅
https://github.com/maraisr/tctx/blob/c4d62510034ae584a111389df878169fb30f249a/validation/test.sh#L16-L17
Im a mega fan of this spec, and love seeing where its going.