Giraffe.ViewEngine

An F# view engine for Giraffe and other ASP.NET Core web applications.

Linux, macOS and Windows Build Status

About

The Giraffe.ViewEngine is a UI framework which uses traditional F# functions and types to build rich HTML or XML based web views. This means that views built with the Giraffe.ViewEngine are automatically compiled into an assembly, don't require any disk I/O to load or render views and users of the Giraffe.ViewEngine can utilise the full power of F# to create custom views in every way possible.

Originally the Giraffe.ViewEngine was part of the Giraffe web framework but has been completely separated since then and can be used on its own with any other .NET Core web application today.

Documentation

Overview

The Giraffe.ViewEngine is an extremely light weight F# DSL (Domain Specific Language) for building HTML.

It is centered around the following types:

type XmlAttribute =
    | KeyValue of string * string
    | Boolean  of string

type XmlElement   = string * XmlAttribute[]    // Name * XML attributes

type XmlNode =
    | ParentNode  of XmlElement * XmlNode list // An XML element which contains nested XML elements
    | VoidElement of XmlElement                // An XML element which cannot contain nested XML (e.g. <hr /> or <br />)
    | Text        of string                    // Text content

The DSL mainly consists of F# functions which will create objects of one of the above defined types. Currently the Giraffe.ViewEngine has functions for all of the standard html tags, such as head, body, h1, etc.

Please see HTML Elements and Attributes for further details and to get a better understanding.

HTML Elements and Attributes

HTML elements and attributes are defined as F# objects:

let indexView =
    html [] [
        head [] [
            title [] [ str "Giraffe Sample" ]
        ]
        body [] [
            h1 [] [ str "I |> F#" ]
            p [ _class "some-css-class"; _id "someId" ] [
                str "Hello World"
            ]
        ]
    ]

A HTML element can either be a ParentNode, a VoidElement or a Text element.

For example the <html> or <div> tags are typical ParentNode elements. They can hold an XmlAttribute list and a second XmlElement list for their child elements:

let someHtml = div [] []

All ParentNode elements accept these two parameters:

let someHtml =
    div [ _id "someId"; _class "css-class" ] [
        a [ _href "https://example.org" ] [ str "Some text..." ]
    ]

Most HTML tags are ParentNode elements, however there is a few HTML tags which cannot hold any child elements, such as <br>, <hr> or <meta> tags. These are represented as VoidElement objects and only accept the XmlAttribute list as single parameter:

let someHtml =
    div [] [
        br []
        hr [ _class "css-class-for-hr" ]
        p [] [ str "bla blah" ]
    ]

Attributes are further classified into two different cases. First and most commonly there are KeyValue attributes:

a [
    _href "http://url.com"
    _target "_blank"
    _class "class1" ] [ str "Click here" ]

As the name suggests, they have a key, such as class and a value such as the name of a CSS class.

The second category of attributes are Boolean flags. There are not many but some HTML attributes which do not require any value (e.g. async or defer in script tags). The presence of such an attribute means that the feature is turned on, otherwise it is turned off:

script [ _src "some.js"; _async ] []

There's also a wealth of accessibility attributes available under the Giraffe.ViewEngine.Accessibility module (needs to be explicitly opened).

Text Content

Naturally the most frequent content in any HTML document is pure text:

<div>
    <h1>This is text content</h1>
    <p>This is even more text content!</p>
</div>

The Giraffe.ViewEngine lets one create pure text content as a Text element. A Text element can either be generated via the rawText or encodedText (or the short alias str) functions:

let someHtml =
    div [] [
        p [] [ rawText "<div>Hello World</div>" ]
        p [] [ encodedText "<div>Hello World</div>" ]
    ]

The rawText function will create an object of type XmlNode where the content will be rendered in its original form and the encodedText/str function will output a string where the content has been HTML encoded.

In this example the first p element will literally output the string as it is (<div>Hello World</div>) while the second p element will output the value as HTML encoded string <div>Hello World</div>.

Please be aware that the the usage of rawText is mainly designed for edge cases where someone would purposefully want to inject HTML (or JavaScript) code into a rendered view. If not used carefully this could potentially lead to serious security vulnerabilities and therefore should be used only when explicitly required.

Most cases and particularly any user provided content should always be output via the encodedText/str function.

Naming Convention

The Giraffe.ViewEngine has a naming convention which lets you easily determine the correct function name without having to know anything about the view engine's implementation.

All HTML tags are defined as XmlNode elements under the exact same name as they are named in HTML. For example the <html> tag would be html [] [], an <a> tag would be a [] [] and a <span> or <canvas> would be the span [] [] or canvas [] [] function.

HTML attributes follow the same naming convention except that attributes have an underscore prepended. For example the class attribute would be _class and the src attribute would be _src in the Giraffe.ViewEngine.

The underscore does not only help to distinguish an attribute from an element, but also avoid a naming conflict between tags and attributes of the same name (e.g. <form> vs. <input form="form1">).

If a HTML attribute has a hyphen in the name (e.g. accept-charset) then the equivalent Giraffe attribute would be written in camel case notion after the initial underscore (e.g. _acceptCharset).

Should you find a HTML tag or attribute missing in the Giraffe.ViewEngine then you can either create it yourself or send a pull request on GitHub.

Javascript event handlers

It is possible to add JavaScript event handlers to HTML elements using the Giraffe.ViewEngine. These event handlers (all prefixed with names starting with _on, for example _onclick, _onmouseover) can either execute inline JavaScript code or can invoke functions that are part of the window scope.

This example illustrates how inline JavaScript could be used to log to the console when a button is clicked:

let inlineJSButton =
    button [_id "inline-js"
            _onclick "console.log(\"Hello from the 'inline-js' button!\");"] [str "Say Hello" ]

There are some caveats with this approach, namely that

...it is not very scalable to write JavaScript inline in this manner, and more pressing...
...the Giraffe.ViewEngine HTML-encodes the text provided to the _onX attributes.

To get around this, you can write dedicated scripts in your HTML and reference the functions from your event handlers:

let page =
    div [] [
        script [_type "application/javascript"] [
            rawText """
            window.greet = function () {
                console.log("ping from the greet method");
            }
            """
        ]
        button [_id "script-tag-js"
                _onclick "greet();"] [str "Say Hello"]
    ]

Here it's important to note that we've included the text of our script using the rawText tag. This ensures that our text is not encoded by the Giraffe.ViewEngine so that it remains as it was written.

However, writing large quantities of JavaScript in this manner can be difficult, because you don't have access to the large ecosystem of javascript editor tooling. In this case you should write your functions in another script and use a script tag element to reference your script, then add the desired function to your HTML element's event handler.

Say you had a JavaScript file named greet.js and had configured Giraffe to serve that script from the WebRoot. Let us also say that the content of that script was:

function greet() {
    console.log("Hello from the greet function of greet.js!");
}

Then, you could reference that javascript via a script element, and use greet in your event handler like so:

let page =
    html [] [
        head [] [
            script [_type "application/javascript"
                    _src "/greet.js"] [] // include our `greet.js` function dynamically
        ]
        body [] [
            button [_id "greet-btn"
                    _onclick "greet()"] [] // use the `greet()` function from `greet.js` to say hello
        ]
    ]

In this way, you can write greet.js with all of your expected tooling, and still hook up the event handlers all in one place in the Giraffe.ViewEngine.

Custom Elements and Attributes

Adding new elements or attributes is normally as simple as a single line of code:

open Giraffe.ViewEngine

// If there was a new <foo></foo> HTML element:
let foo = tag "foo"

// If <foo> is an element which cannot hold any content then create it as voidTag:
let foo = voidTag "foo"

// If <foo> has a new attribute called bar then create a new bar attribute:
let _bar = attr "bar"

// if the bar attribute is a boolean flag:
let _bar = flag "bar"

Alternatively you can also create new elements and attributes from inside another element:

let someHtml =
    div [] [
        tag "foo" [ attr "bar" "blah" ] [
            voidTag "otherFoo" [ flag "flag1" ]
        ]
    ]

Rendering Views

Rendering views with the Giraffe.ViewEngine can be done in several ways. The RenderView module exposes three sub modules which can be used to specify the desired output format:

RenderView.IntoStringBuilder implements functions to render a view into a StringBuilder object which can be used for further processing.
RenderView.AsString implements functions to output a view directly as a string.
RenderView.AsBytes implements functions to output a view directly as a byte array.

All three sub modules implement the following public functions:

htmlDocument
htmlNodes
htmlNode
xmlNodes
xmlNode

Rendering HTML

The htmlDocument function takes a single XmlNode as input parameter and renders a HTML page with a DOCTYPE declaration. This function should be used for rendering a complete HTML document.

The htmlNodes function takes an XmlNode list as input parameter and will output a single HTML string containing all the rendered HTML code. The htmlNode function renders a single XmlNode element into a valid HTML string. Both, the htmlNodes and htmlNode function are useful for use cases where a HTML snippet needs to be created without a DOCTYPE declaration (e.g. email templates, etc.).

Rendering XML

Views cannot only be rendered into HTML pages but also into other XML based content such as SVG images or other data objects.

The xmlNodes and xmlNode function are identical to htmlNodes and htmlNode, except that they will render void elements differently:

let someTag = voidTag "foo"
let someContent = someTag []

// Void tag will be rendered to valid HTML: <foo>
let output1 = RenderView.AsString.htmlNode someContent

// Void tag will be rendered to valid XML: <foo />
let output2 = RenderView.AsString.xmlNode someContent

StringBuilder Pools

All functions from the RenderView.AsString and RenderView.AsBytes modules are using a thread static StringBuilderPool to avoid the creation of large StringBuilder objects for each render call and dynamically grow/shrink that pool based on the application's needs. However if the application is running into any memory issues then this performance feature can be disabled by setting StringBuilderPool.IsEnabled to false:

StringBuilderPool.IsEnabled <- false

Additionally the RenderView.IntoStringBuilder module can be used if full control of the StringBuilder object is required:

open System.Text
open Giraffe.ViewEngine

let someHtml =
    div [] [
        tag "foo" [ attr "bar" "blah" ] [
            voidTag "otherFoo" [ flag "flag1" ]
        ]
    ]

// Create your own StringBuilder, which gives the caller
// full control of the lifecycle of the object:
let sb = new StringBuilder()

// Perform actions on the `sb` object...
sb.AppendLine "This is a HTML snippet inside a markdown string:"
  .AppendLine ""
  .AppendLine "```html" |> ignore

// Using RederView.IntoStringBuilder some HTML content can be written
// directly into the given StringBuilder object:
let sb' = RederView.IntoStringBuilder.htmlNode sb someHtml

// Perform more actions on the `sb` object...
sb'.AppendLine "```" |> ignore

let markdownOutput = sb'.ToString()

Common Patterns

The Giraffe.ViewEngine is nothing more but simple F# code dressed up as a DSL which can be used to compose rich HTML content in a structured way. As such it doesn't require any built-in functions to enable common view engine features such as master pages, partial views or model binding. These things can all be accomplished through normal F# coding patterns:

Master Pages

Creating a master page is as simple as piping two functions together:

module Views =
    open Giraffe.ViewEngine

    let master (pageTitle : string) (content: XmlNode list) =
        html [] [
            head [] [
                title [] [ str pageTitle ]
            ]
            body [] content
        ]

    let index =
        let pageTitle = "Giraffe Sample"
        [
            h1 [] [ str pageTitle ]
            p [] [ str "Hello world!" ]
        ] |> master pageTitle

... or even have multiple nested master pages:

module Views =
    open Giraffe.ViewEngine

    let master1 (pageTitle : string) (content: XmlNode list) =
        html [] [
            head [] [
                title [] [ str pageTitle ]
            ]
            body [] content
        ]

    let master2 (content: XmlNode list) =
        [
            main [] content
            footer [] [
                p [] [
                    str "Copyright ..."
                ]
            ]
        ]

    let index =
        let pageTitle = "Giraffe Sample"
        [
            h1 [] [ str pageTitle ]
            p [] [ str "Hello world!" ]
        ] |> master2 |> master1 pageTitle

Partial Views

Partial views can be codified by calling one function from within another:

module Views =
    open Giraffe.ViewEngine

    let partial =
        footer [] [
            p [] [
                str "Copyright..."
            ]
        ]

    let master (pageTitle : string) (content: XmlNode list) =
        html [] [
            head [] [
                title [] [ str pageTitle ]
            ]
            body [] content
            partial
        ]

    let index =
        let pageTitle = "Giraffe Sample"
        [
            h1 [] [ str pageTitle ]
            p [] [ str "Hello world!" ]
        ] |> master pageTitle

Model Binding

A view which accepts a model is basically a function with an additional parameter:

module Views =
    open Giraffe.ViewEngine

    let partial =
        footer [] [
            p [] [
                str "Copyright..."
            ]
        ]

    let master (pageTitle : string) (content: XmlNode list) =
        html [] [
            head [] [
                title [] [ str pageTitle ]
            ]
            body [] content
            partial
        ]

    let index (model : IndexViewModel) =
        [
            h1 [] [ str model.PageTitle ]
            p [] [ str model.WelcomeText ]
        ] |> master model.PageTitle

Logical Constructs

Things like if statements, loops and other F# language constructs just work as expected:

let partial (books : Book list) =
    ul [] [
        yield!
            books
            |> List.map (fun b -> li [] [ str book.Title ])
    ]

Overall the Giraffe.ViewEngine is extremely flexible and more feature rich than any other view engine given that it is just normal compiled F# code.

Best Practices

Due to the huge amount of available HTML tags and their fairly generic (and short) names (e.g. <form>, <option>, <select>, etc.) there is a significant danger of accidentally overriding a function of the same name in an application's codebase. For that reason the Giraffe.ViewEngine becomes only available after opening the Giraffe.ViewEngine module.

As a measure of good practice it is recommended to create all views in a separate module:

module MyWebApplication

module Views =
    open Giraffe.ViewEngine

    let index =
        html [] [
            head [] [
                title [] [ str "Giraffe Sample" ]
            ]
            body [] [
                h1 [] [ str "I |> F#" ]
                p [ _class "some-css-class"; _id "someId" ] [
                    str "Hello World"
                ]
            ]
        ]

    let other = //...

This ensures that the opening of the Giraffe.ViewEngine is only contained in a small context of an application's codebase and therefore less of a threat to accidental overrides. In the above example views can always be accessed through the Views sub module (e.g. Views.index).

Samples

The following sample code creates and renders a HTML page with the help of the Giraffe.ViewEngine and subsequently saves it into a temporary .html file before opening it with the default browser:

module Sample =
    open Giraffe.ViewEngine

    let bodyTemplate (nameList: string list): XmlNode =
        body []
            [ h1 [] [ Text "Welcome:" ]
              ol [] (nameList |> List.map (fun x -> li [] [ Text x ])) ]

    let navTemplate =
        nav [] [ a [ _href "./About" ] [ Text "About" ] ]

    let documentTemplate (nav: XmlNode) (body: XmlNode) =
        html [] [ nav; body ]

    let render welcomeUsers =
        bodyTemplate welcomeUsers
        |> (documentTemplate navTemplate)
        |> RenderView.AsString.htmlDocument

[<EntryPoint>]
let main args =
    let tfn =
        (System.IO.Path.GetTempFileName()) |> sprintf "%s.html"

    args
    |> Seq.toList
    |> Sample.render
    |> fun x -> System.IO.File.WriteAllText(tfn, x)
    |> ignore

    let p = new System.Diagnostics.Process()
    p.StartInfo.FileName <- tfn
    p.StartInfo.UseShellExecute <- true
    p.Start() |> ignore

    0

The above code will return the following result:

This sample application can also be viewed inside the Giraffe.ViewEngine.Sample application.

Attribution to original authors

This code has been originally ported from Suave and subsequently improved and extended over the years.

The original code has been authored by

You can find the original implementation here:

https://github.com/SuaveIO/suave/blob/master/src/Suave.Experimental/Html.fs

Huge thanks to Suave for letting us borrow their code and thanks to Florian Verdonck for originally porting it to Giraffe.

Nightly builds and NuGet feed

All official release packages are published to the official and public NuGet feed.

Nightly builds (builds from the develop branch) produce unofficial pre-release packages which can be pulled from the project's NuGet feed on GitHub.

These packages are being tagged with the Workflow's run number as the package version.

All other builds, such as builds triggered by pull requests produce a NuGet package which can be downloaded as an artifact from the individual GitHub action.

License

Apache 2.0

Name		Name	Last commit message	Last commit date
Latest commit History 86 Commits
.github/workflows		.github/workflows
samples/Giraffe.ViewEngine.Sample		samples/Giraffe.ViewEngine.Sample
src/Giraffe.ViewEngine		src/Giraffe.ViewEngine
tests		tests
.gitattributes		.gitattributes
.gitignore		.gitignore
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
Giraffe.ViewEngine.sln		Giraffe.ViewEngine.sln
LICENSE		LICENSE
NuGet.config		NuGet.config
README.md		README.md
RELEASE_NOTES.md		RELEASE_NOTES.md
giraffe-64x64.png		giraffe-64x64.png

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Giraffe.ViewEngine

Linux, macOS and Windows Build Status

Table of contents

About

Documentation

Overview

HTML Elements and Attributes

Text Content

Naming Convention

Javascript event handlers

Custom Elements and Attributes

Rendering Views

Rendering HTML

Rendering XML

StringBuilder Pools

Common Patterns

Master Pages

Partial Views

Model Binding

Logical Constructs

Best Practices

Samples

Attribution to original authors

Nightly builds and NuGet feed

License

About

Releases 7

Packages

Contributors 11

Languages

License

giraffe-fsharp/Giraffe.ViewEngine

Folders and files

Latest commit

History

Repository files navigation

Giraffe.ViewEngine

Linux, macOS and Windows Build Status

Table of contents

About

Documentation

Overview

HTML Elements and Attributes

Text Content

Naming Convention

Javascript event handlers

Custom Elements and Attributes

Rendering Views

Rendering HTML

Rendering XML

StringBuilder Pools

Common Patterns

Master Pages

Partial Views

Model Binding

Logical Constructs

Best Practices

Samples

Attribution to original authors

Nightly builds and NuGet feed

License

About

Topics

Resources

License

Code of conduct

Stars

Watchers

Forks

Releases 7

Packages 0

Contributors 11

Languages

Packages