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

Better debugging #27

Open
breezykermo opened this issue Dec 12, 2018 · 1 comment
Open

Better debugging #27

breezykermo opened this issue Dec 12, 2018 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@breezykermo
Copy link
Member

Debugging is quite impractical at the moment. It basically consists of adding console.logs in each of the classes until the error is palpable.

It would be much nicer to be able to toggle on a 'debug' mode, which either:

  • prints a range of console.log statements so that you know which function has been called
  • handles error location through some other setup.

The main issue is that errors are difficult to locate, and require explicit tracing from the route down through the file hierarchy.

@breezykermo breezykermo added enhancement New feature or request help wanted Extra attention is needed release Currently in progress for next release and removed release Currently in progress for next release labels Dec 12, 2018
@jlieb10
Copy link
Contributor

jlieb10 commented Dec 14, 2018

👍 agreed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants