safe-stack

SAFE Stack

Specific best practices and architectural patterns when working with SAFE Stack.

Details

Language / Topic
fsharpF#
Category
framework

Rules

balanced
- Partition logic definitively storing server algorithms in `Server` and client functions in `Client` directories.
- Expose backend APIs explicitly defining `Fable.Remoting` interfaces generating fully typed client RPC definitions.
- Share domain models identically configuring standard record types successfully across both client and server compilations.
- Configure build pipelines safely evaluating the standard FAKE build script orchestrating continuous compilation processes.