-
Notifications
You must be signed in to change notification settings - Fork 55
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
js uses not defined value #329
Comments
Suave is the web server - it runs on .NET and you should not compile it with Fable. |
well, that explains it then. So if suave is strictly .net and Fable is a F#
to JS transpiler, what exactly is Fable.Remoting.Suave? An opinionated way
on how to work with suave? And why is it in the Fable namespace if it's not
supposed to interact with fable?
…On Tue, Nov 15, 2022, 21:38 kerams ***@***.***> wrote:
Suave is the web server - it runs on .NET and you should not compile it
with Fable.
—
Reply to this email directly, view it on GitHub
<#329 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACOHZTQ3DPTMJ4VFX3TBSX3WIPYDLANCNFSM6AAAAAASBKVLNY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Fable.Remoting.Client package is what you use in the client project which you compile with Fable. Fable.Remoting.(Suave | Giraffe | etc.) on the other hand are purely .NET packages, which are to be used in the corresponding web server, so that it knows how to handle the Remoting RPC traffic. Both sides are needed - it does not make sense to use one without the other. Fable.Remoting is the name of this project and therefore it is also the main namespace for all Nuget packages, even though most of them aren't technically Fable-compatible. |
even though most of them aren't technically Fable-compatible.
interesting, and a bit confusing. Nevertheless, thanks for the explanation.
Coming from the js side, maybe that could be highlighted in the docs?
Feel free to close this issue though, otherwise I'll do it once I'm at home
again
…On Tue, Nov 15, 2022, 22:07 kerams ***@***.***> wrote:
Fable.Remoting.Client package is what you use in the client project which
you compile with Fable. Fable.Remoting.(Suave | Giraffe | etc.) on the
other hand are purely .NET packages, which are to be used in the
corresponding web server, so that it knows how to handle the Remoting RPC
traffic. Both sides are needed - it does not make sense to use one without
the other. Fable.Remoting is the name of this project and therefore it is
also the main namespace for all Nuget packages, even though most of them
aren't technically Fable-compatible.
—
Reply to this email directly, view it on GitHub
<#329 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACOHZTXPOCSBL6SZ24G6Z3TWIP3QTANCNFSM6AAAAAASBKVLNY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi, I'm just trying to get started with Fable (coming from JS) in general and thought Fable.Remoting looked really nice.
However it seems that following the "from scratch" guide for suave produces broken JS and I don't know why.
.fsproj
Server.fs
Server.fs.js
Fable_Remoting_Suave_Remoting_buildWebPart
obviously doesn't exist in the scope where it's used. Any ideas why and what I did wrong?The text was updated successfully, but these errors were encountered: