microsoft / microsoft/node-api-dotnet
Marshalling: Exception subclasses
Open
Nobody has claimed this yet.
enhancement
marshalling
- Dominant language
- C#
- Stars
- 783
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
For example, if in .NET I have this:
throw new FormatException("invalid input");
then in Node, can I know that the Error is caused by "FormatException"?
It seems this feature is missing so that the only way is to check the "message" property of the Error object?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by locating the .NET-to-Node error marshalling path and determine how exception subclasses are currently represented. Done means a Node-side Error can identify that the original exception was a FormatException without relying on its message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, node.js
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100