Support subscription operation logging with custom log level #110
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
boblat
approved these changes
Oct 20, 2023
boblat
approved these changes
Oct 20, 2023
…udit) plus tweak logGraphQLOperation output
…te doc to refer to the tsdoc of the input type.
cuzzlor
force-pushed
the
support-subscription-operation-logging-with-custom-log-level
branch
from
1fa9505
to
97da08d
Compare
cuzzlor
deleted the
support-subscription-operation-logging-with-custom-log-level
branch
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.
What ?
Over in the graphql-apollo-server lib we recently tweaked the graphql operation logging plugin to support a little more output plus make the log level configurable.
This PR:
audit)logGraphQLOperationmethod vialogSubscriptionOperation, aligning output somewhat to what thegraphql-apollo-server#graphqlOperationLoggingPluginproduces