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.

Sign up for GitHub

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

Jump to bottom

Output stack trace for errors in debug mode #137

Merged
merged 5 commits into from
Sep 12, 2016
Merged

Output stack trace for errors in debug mode #137

merged 5 commits into from
Sep 12, 2016

Conversation

nnance
Copy link
Contributor

@nnance nnance commented Sep 11, 2016 •
edited
Loading

This resolves #111

TODO:

  • Update CHANGELOG.md with your change (include reference to issue & this PR)
  • Make sure all of the significant new logic is covered by tests
  • Rebase your changes on master so that they can be merged easily
  • Make sure all tests and linter rules pass

@nnance nnance added this to the 0.3 milestone Sep 11, 2016
@helfer
Copy link
Contributor

helfer commented Sep 12, 2016

Awesome! We should add this to the docs as well now.

@helfer helfer merged commit f4546e7 into master Sep 12, 2016
@helfer helfer removed the ready label Sep 12, 2016
@nnance
Copy link
Contributor Author

nnance commented Sep 13, 2016

Will do

@helfer helfer deleted the debug-mode branch September 13, 2016 05:28
trevor-scheer pushed a commit that referenced this pull request May 6, 2020
@renovate
chore(deps): update dependency @types/node-fetch to v2.3.5 (#137)
99a5ede
trevor-scheer pushed a commit that referenced this pull request May 14, 2020
@renovate
chore(deps): update dependency @types/node-fetch to v2.3.5 (#137)
a98b31f
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.3
Development

Successfully merging this pull request may close these issues.

Print stack trace of graphql errors when debugging
3 participants
@nnance @helfer @zol