Open daytonjallen opened 1 year ago
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.
Hey @mkArtakMSFT, I would like to work on this issue.
@shiladitya-mukerji-22 I just found your message accidentally. If you want, you can wait for us to drop a summary comment, which will hopefully give you hints regarding how to proceed and what approach to take. If you are confident that you can handle it without it, feel free to send us a PR and we'll get somebody review it.
Thanks for contacting us.
We're moving this issue to the .NET 9 Planning
milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.
Is there an existing issue for this?
Describe the bug
Calling an asynchronous .NET JS Interop method synchronously produces an unhelpful/misleading error message.
These error messages (shown in steps to reproduce section) makes debugging the problem not very clear and seem mostly related to JSON Serialization - whereas that might not be the case.
Expected Behavior
Error message should indicate that this is an (unsupported workflow?) and warn against invoking async methods synchronously from JS or something that makes it easier to identify what the issue is.
Steps To Reproduce
Repo reproducing problem here: https://github.com/daytonjallen/JsonExceptionRepro
Functions executes "successfully" and produces an exception in the console:
Also the error is different if we pass parameters:
Exceptions (if any)
Without Params:
With Params:
.NET Version
7.0.200
Anything else?
Visual Studio Version: 17.5.0