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

Debugging wishlist meta-issue #13177

Closed
foldleft opened this issue Apr 15, 2020 · 2 comments
Closed

Debugging wishlist meta-issue #13177

foldleft opened this issue Apr 15, 2020 · 2 comments
Labels
A-Developer-Experience O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement

Comments

@foldleft
Copy link
Contributor

  • Log lines should indicate the file/function they came from
  • The flow of user activity should be easily followed –– and parsed
  • We should try to preserve context –– logging the traceback as well as an error if we use console.error
@t3chguy
Copy link
Member

t3chguy commented Apr 15, 2020

Log lines should indicate the file/function they came from

This is possible if you Blackbox rageshake.js in devtools

@andybalaam andybalaam added S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement A-Developer-Experience O-Occasional Affects or can be seen by some users regularly or most users rarely labels May 20, 2022
@Johennes
Copy link
Contributor

Closing as this hasn't received a lot of traction in the past three years.

@Johennes Johennes closed this as not planned Won't fix, can't repro, duplicate, stale Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Developer-Experience O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement
Projects
None yet
Development

No branches or pull requests

5 participants