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

introduce RequestContext#Validate and use it instead of NewRequestContext function #828

Merged
merged 3 commits into from
Sep 24, 2019

Conversation

vvakame
Copy link
Collaborator

@vvakame vvakame commented Aug 13, 2019

closes #804

Describe your PR and link to any relevant issues.
improve information at RequestContext for rich logging.
We are talking this change in #804

I have:

  • Added tests covering the bug / feature (see testing)
  • Updated any relevant documentation (see docs)

@vvakame vvakame changed the title Feat rc introduce RequestContext#Validate and use it instead of NewRequestContext function Aug 13, 2019
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 61.66% when pulling 82758be on feat-rc into 6b70be0 on master.

@JulienBreux
Copy link

🙏 Thanks

@vektah vektah merged commit cc64f33 into master Sep 24, 2019
@vektah vektah deleted the feat-rc branch September 24, 2019 10:08
cgxxv pushed a commit to cgxxv/gqlgen that referenced this pull request Mar 25, 2022
introduce RequestContext#Validate and use it instead of NewRequestContext function
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

improve information at RequestContext for rich logging
4 participants