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 Feb 27, 2023. It is now read-only.
This can make sense if we have custom Exception when possible (with custom fields, etc.) to make it easier to access the Error/Exception info.
Otherwise not sure to see the difference between JS.Error and Exception.
Would this cause some problems/conflicts in the error definition for third parties libs ?
Fable translates .NET System.Exception to JS Error and makes equivalence between the Message and StackTrace property (reference). So the proposal makes sense :)
When you define a custom exception it will extend JS Error in generated code, but I'm not sure right now how that would work in the bindings, haven't tried yet 🤔
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since F# has
System.Exception
, I'm wondering if we should just use that (and extend it where necessary) in the node bindings.The text was updated successfully, but these errors were encountered: