Skip to content
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 Apollo tracing spec support #84

Merged
merged 1 commit into from
Jul 16, 2024

Conversation

swalkinshaw
Copy link
Contributor

Apollo's tracing spec has long been deprecated. This removes support for offset timestamps which were only needed for Apollo tracing.

Dropping these offsets simplifies our code and lets us store an array of resolver timing duration timestamps instead of hashes as well.

This is a breaking change. However, at least internally at Shopify, we never consumed these offsets.

Note: I'm extracting a few cleanups/changes from #81 to ship them separately.

@swalkinshaw swalkinshaw requested a review from a team July 15, 2024 19:56
@time_since_offset = time_since_offset
@result = result
end
[result, duration]
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I could keep a simplified TimedResult which is better for readability, but figured the array/tuple is simpler

Apollo's tracing [spec](https://github.com/apollographql/apollo-tracing)
has long been deprecated. This removes support for `offset` timestamps
which were only needed for Apollo tracing.

Dropping these offsets simplifies our code and lets us store an array of
resolver timing duration timestamps instead of hashes as well.
@swalkinshaw swalkinshaw force-pushed the remove-apollo-tracing-spec-support branch from 9c075ea to 8f96cf2 Compare July 15, 2024 20:09
@swalkinshaw swalkinshaw merged commit 2d2a51c into main Jul 16, 2024
30 checks passed
@swalkinshaw swalkinshaw deleted the remove-apollo-tracing-spec-support branch July 16, 2024 13:40
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.

3 participants