-
Notifications
You must be signed in to change notification settings - Fork 2k
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
apollo-engine-reporting: direct path string building #3479
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.
Good catch! I'm certain this would be more efficient.
I've left a couple comments within. This needs a - apollo-engine-reporting:
CHANGELOG.md
entry (which we'll add before merging if you don't have one in mind) and my only other firm ask is that we add the comment in-line for posterity's sake.
} from 'graphql'; | ||
import { Trace, google } from 'apollo-engine-reporting-protobuf'; | ||
import { GraphQLError, GraphQLResolveInfo, ResponsePath } from 'graphql'; | ||
import { google, Trace } from 'apollo-engine-reporting-protobuf'; |
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.
Strongly prefer keeping these no-op, one-off changes out of change sets, but not asking you to revert it.
(I low-key wish there were |
I don't know the difference :D Co-Authored-By: Jesse Rosenberger <git@jro.cc>
Thanks Co-Authored-By: Jesse Rosenberger <git@jro.cc>
I don't have performance numbers, but creating those arrays and reversing them could be worth avoiding.