A Functional Web with ASP.NET Core and F#'s Giraffe

I was watching Ody Mbegbu's YouTube Channel - it's filled with .NET Core and ASP.NET Tutorial Videos - and was checking out one in particular, "Getting Started with ASP.NET Core Giraffe." Dane Vinson pointed me to it.

There is such a great open source renaissance happening right now with new framework's and libraries popping up in the .NET Core space. I hope you check them out AND support the creators by getting involved, writing docs, filing (kind) issues, and even doing pull requests and fixing bugs or writing tests.

Ody's video was about Dustin Morris' "Giraffe" web framework. Dustin's description is "A native functional ASP.NET Core web framework for F# developers." You can check it out over at https://github.com/dustinmoris/Giraffe.

Even better, it uses the "dotnet new" templating system so you can check it out and get started in seconds.

c:> md \mygiraffeeapp & cd \mygiraffeeapp

c:\mygiraffeeapp> dotnet new -i "giraffe-template::*"

c:\mygiraffeeapp> dotnet new giraffe

The template "Giraffe Web App" was created successfully.

c:\mygiraffeeapp> dotnet run

Hosting environment: Production

Content root path: C:\mygiraffeapp

Now listening on: http://localhost:5000

Application started. Press Ctrl+C to shut down.

Boom. Now I'm checking out Giraffe's "Hello World."

Because ASP.NET Core is very modular and built on "middleware" pipelines, that means that other frameworks like Giraffe can use the bits they want and remove the bits they down. Remembering that this is F#, not C#, here you can see Giraffe adding itself to the pipeline while still using the StaticFileMiddleware.

let configureApp (app : IApplicationBuilder) =

    app.UseGiraffeErrorHandler errorHandler

    app.UseStaticFiles() |> ignore

    app.UseGiraffe webApp

The initial readme.md for Giraffe is the docs for now, and frankly, they are excellent and easy to read. The author says:

It is not designed to be a competing web product which can be run standalone like NancyFx or Suave, but rather a lean micro framework which aims to complement ASP.NET Core where it comes short for functional developers. The fundamental idea is to build on top of the strong foundation of ASP.NET Core and re-use existing ASP.NET Core building blocks so F# developers can benefit from both worlds.

Here is a smaller Hello World. Note the use of choose and the clear and terse nature of F#:

open Giraffe.HttpHandlers

open Giraffe.Middleware



let webApp =

    choose [

        route "/ping"   >=> text "pong"

        route "/"       >=> htmlFile "/pages/index.html" ]



type Startup() =

    member __.Configure (app : IApplicationBuilder)

                        (env : IHostingEnvironment)

                        (loggerFactory : ILoggerFactory) =



        app.UseGiraffe webApp

Is terse an insult? Absolutely not, it's a feature! Check out this single line exampe...and the fish >=> operator! Some people don't like it but I think it's clever.

let app = route "/" >=> setStatusCode 200 >=> text "Hello World"

Making more complex:

let app =

    choose [

        GET  >=> route "/foo" >=> text "GET Foo"

        POST >=> route "/foo" >=> text "POST Foo"

        route "/bar" >=> text "Always Bar"

    ]

Or requiring certain headers:

let app =

    mustAccept [ "text/plain"; "application/json" ] >=>

        choose [

            route "/foo" >=> text "Foo"

            route "/bar" >=> json "Bar"

        ]

And you can continue to use Razor views as you like, passing in models written in F#

open Giraffe.Razor.HttpHandlers



let model = { WelcomeText = "Hello World" }



let app =

    choose [

        // Assuming there is a view called "Index.cshtml"

        route  "/" >=> razorHtmlView "Index" model

    ]

There are samples at https://github.com/dustinmoris/Giraffe/tree/master/samples you can check out as well

* Giraffe photo by Kurt Thomas Hunt, used under CC

Sponsor: A third of teams don’t version control their database. Connect your database to your version control system with SQL Source Control and find out who made changes, what they did, and why. Learn more!