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

getDebugInfo tweaks #356

Open
1 of 5 tasks
rwjblue opened this issue Oct 26, 2018 · 2 comments
Open
1 of 5 tasks

getDebugInfo tweaks #356

rwjblue opened this issue Oct 26, 2018 · 2 comments

Comments

@rwjblue
Copy link
Collaborator

rwjblue commented Oct 26, 2018

After playing around with .getDebugInfo() a bit, I'd like to see a few changes:

  • Better output when calling .getDebugInfo() where Ember.run.backburner.DEBUG is not set. Perhaps even returning the data that we do have (which is essentially everything except the stacks).
  • When the scheduled timers are scheduled to fire (essentially executeAt info).
  • Are we flushing currently?
  • Is the current flush due to an autorun?
  • Is a future autorun scheduled? Adding autorun stack to debug info #361
@rwjblue
Copy link
Collaborator Author

rwjblue commented Oct 26, 2018

/cc @scalvert

@scalvert
Copy link
Contributor

Seems reasonable.

I'm torn about

Better output when calling .getDebugInfo() where Ember.run.backburner.DEBUG is not set

(and thought about this when I was implementing) because would one expect to get debug info when not in DEBUG mode? If we go that route, we may want to think about different naming for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants