search

dotnet / aspnetcore

ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
https://asp.net
MIT License
35.21k stars 9.95k forks source link

Generate typescript type definitions for invoking jsinvokable methods #40499

Open unicomp21 opened 2 years ago

unicomp21 commented 2 years ago

Is there an existing issue for this?

Is your feature request related to a problem? Please describe the problem.

When generating webassembly from rust, it will also generate typescript bindings. Maybe Blazor could do the same?

Initial thinking would be to generate typescript bindings for anything marked w/ jsinvokable. Generating jsdoc bindings could be useful as well.

Describe the solution you'd like

Anything in my .net library marked w/ jsinvokable, which is compiled to webassembly, can be called via typescript bindings which are generated. For a great example, see how rust generates typescript bindings for rust which has been compiled to webassembly.

Additional context

No response

ghost commented 2 years 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.

Aloento commented 2 years ago

https://github.com/Elringus/DotNetJS

ghost commented 2 years ago

Thanks for contacting us.

We're moving this issue to the .NET 8 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.

ghost commented 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.

ghost commented 9 months ago

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.

yugabe commented 9 months ago

Slightly related, TypeScript type definitions for the Blazor object (not for interop): https://github.com/podNET-Hungary/blazor-typings

mkArtakMSFT commented 8 months ago

Part of https://github.com/dotnet/aspnetcore/issues/52819