-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fable.Remoting.Falco support #312
Comments
Cannot wait. Are there any problems? Is there draft somewhere? I'm curious how much work is needed. |
It has been slow going, I'll admit. I have a lot on my plate right now at
home, work and with my own OSS. So I haven't done as much as I would like.
My fork is where you'd find what I've done. It is here:
https://github.com/pimbrouwers/Fable.Remoting
I am not well versed in this space anyway, so if you want to take it over.
By all means!
…On Fri., Sep. 30, 2022, 6:26 a.m. Tomasz Olęcki, ***@***.***> wrote:
Cannot wait. Are there any problems? Is there draft somewhere? I'm curious
how much work is needed.
—
Reply to this email directly, view it on GitHub
<#312 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABDB57N7MKNF4WQ537VOGV3WA255XANCNFSM57FDN2DA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I am also curious about this. Seems like Falco is a very good solution for a Web API project. I am sure Falco would be much more adopted if this use case was covered. |
I would love to see this as well. Admittedly I don't use this tech at all, so this is foreign territory for me. I'd be happy to code review if someone wanted to take the reigns on this. In saying that, and Zaid correct me if I'm wrong, but there is a "standard" aspnet core implementation of this, which would be plugged into Falco very easily. Anything that aspnetcore supports, Falco does as well. |
Indeed, the Fable.Remoting.AspNetCore allows you to integrate Fable.Remoting in any AspNetCore-supported framework. |
Would love to see this. Will submit a PR soon.
Opening an issue only to serve as a placeholder to avoid someone doubling this work.
The text was updated successfully, but these errors were encountered: