You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
I'm a creator of autocomplete-elixir package and I get plenty issue reports weekly. The problem is the stack trace is not always as verbose as I would like it to be.
Wouldn't it be possible to send all local variable values when sending a report?
I guess it'd help a lot of plugin developers.
Cheers
The text was updated successfully, but these errors were encountered:
would be cool to have this issue resolved sometimes soon.
I think the notification popup should allow to click a button for gathering additional data, ready to send / use for plugin developers. not sure if notification package should be responsible for such data gatherings.
Perhaps packages could include an optional onException function that would be called when an exception is traced back to that package. This would give the package author a chance to customize the information that is provided.
Hey there!
I'm a creator of autocomplete-elixir package and I get plenty issue reports weekly. The problem is the stack trace is not always as verbose as I would like it to be.
Wouldn't it be possible to send all local variable values when sending a report?
I guess it'd help a lot of plugin developers.
Cheers
The text was updated successfully, but these errors were encountered: