Oxpecker.ViewEngine 1.0.1

dotnet add package Oxpecker.ViewEngine --version 1.0.1                
NuGet\Install-Package Oxpecker.ViewEngine -Version 1.0.1                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Oxpecker.ViewEngine" Version="1.0.1" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Oxpecker.ViewEngine --version 1.0.1                
#r "nuget: Oxpecker.ViewEngine, 1.0.1"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Oxpecker.ViewEngine as a Cake Addin
#addin nuget:?package=Oxpecker.ViewEngine&version=1.0.1

// Install Oxpecker.ViewEngine as a Cake Tool
#tool nuget:?package=Oxpecker.ViewEngine&version=1.0.1                


Oxpecker.ViewEngine

Oxpecker.ViewEngine is code-as-markup engine used to render your HTML views based on the F# feature called Computation Expressions.

Medium article: 7 reasons to try Oxpecker.ViewEngine

Nuget package dotnet add package Oxpecker.ViewEngine

Markup example:

open Oxpecker.ViewEngine

type Person = { Name: string }

let subView = p() { "Have a nice day" }

let mainView (model: Person) =
    html() {
        body(style="width: 800px; margin: 0 auto") {
            h1(style="text-align: center; color: red") {
                $"Hello, {model.Name}!"
            }
            subView
            ul() {
                for i in 1..10 do
                    br()
                    li().attr("onclick", $"alert('Test {i}')") {
                        span(id= $"span{i}", class'="test") { $"Test {i}" }
                    }
            }
        }
    }

Documentation:

HtmlElement

HtmlElement is a main interface of Oxpecker.ViewEngine. It's extended by two additional interfaces HtmlTag and HtmlContainer:

    type HtmlElement =
        abstract member Render: StringBuilder -> unit
    type HtmlTag =
        inherit HtmlElement
        abstract member AddAttribute: HtmlAttribute -> unit
    type HtmlContainer =
        inherit HtmlElement
        abstract member AddChild: HtmlElement -> unit
    ...

There are 5 types of HTML elements available: RegularNode, VoidNode (only attributes), FragmentNode (only children), RegularTextNode(escaped text), RawTextNode(unescaped text).

All HTML tags inherit from RegularNode or VoidNode and you can easily create your own tag:

type myTag() =
    inherit RegularNode("myTag") // will render <myTag></myTag>

HtmlElement holds two collections inside: attributes and children. More on them below.

Children

Regular nodes can have children that will be added to children collection as you write them between curly braces. Void nodes and Text nodes don't have children. You can programmatically access Chidren property of any HtmlContainer.

let result = div() {
    br()
    span() { "Some text" }
}

let children = result.Children // br and span

Attributes

Regular and Void nodes can have attributes. Some general attributes are defined inside HtmlElement while each tag can have it's specific attributes. This will prevent you from assigning attributes to the element that it doesn't support. You can programmatically access Attributes property of any HtmlTag.

let result = div(class'="myClass") {
    br(id="1234") // href attribute won't work here
    a(href="/") { "Some link" }
}

let children = result.Attributes // class=myClass

You can also attach any custom attribute to the HtmlElement using .attr method:

div().attr("my-secret-key", "lk23j4oij234"){
    "Secret div"
}

For data-* attributes you can use dedicated method:

div().data("secret-key", "lk23j4oij234"){
    "Secret div"
} // renders <div data-secret-key="lk23j4oij234">Secret div</div>

Event handlers

Oxpecker.ViewEngine doesn't provide attributes for javascript event handlers like onclick. This is done on purpose, since it would encourage people using them, which is rather an antipattern. However, if you really need it, you can always use .on method to achieve same goal.

ViewEngine will create html attribute with inline handler for you:

div().on("click", "alert('Hello')"){
    "Clickable div"
}
// <div onclick="alert('Hello')">Clickable div</div>

HTML escaping

Oxpecker.ViewEngine will escape text nodes and attribute values for you. However, sometimes it's desired to render unescaped html string, in that case raw function is provided

div(){
    "<script></script>" // This will be escaped
    raw "<script></script>" // This will NOT be escaped
}

Rendering

There are several functions to render HtmlElement (after opening Oxpecker.ViewEngine namespace):

  • Render.toString will render to standard .NET UTF16 string
  • Render.toBytes will render to UTF8-encoded byte array
  • Render.toStreamAsync will asynchronously render to stream in UTF8 encoding
  • Render.toTextWriterAsync will asynchronously render to the provided text writer
  • Render.toHtmlDocBytes is the same as Render.toBytes, but will also prepend "<!DOCTYPE html>" to the HTML document
  • Render.toHtmlDocString is the same as Render.toString, but will also prepend "<!DOCTYPE html>" to the HTML document
  • Render.toHtmlDocStreamAsync is the same as Render.toStreamAsync, but will also prepend "<!DOCTYPE html>" to the HTML document
  • Render.toHtmlDocTextWriterAsync is the same as Render.toTextWriterAsync, but will also prepend "<!DOCTYPE html>" to the HTML document

Aria

To enable ARIA attributes support you need to open Aria module:

open Oxpecker.ViewEngine.Aria

let x = span(
    role="checkbox",
    id="checkBoxInput",
    ariaChecked="false",
    tabindex=0,
    ariaLabelledBy="chk15-label"
)

Fragments

Sometimes you need to group several elements together without wrapping them in div or similar. You can use Fragment special tag for that:

let onlyChildren = Fragment() {
    span() { "one" }
    span() { "two" }
}

let parent = div() {
    onlyChildren
} // renders <div><span>one</span><span>two</span></div>

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (2)

Showing the top 2 NuGet packages that depend on Oxpecker.ViewEngine:

Package Downloads
Oxpecker

F# web framework built on top of ASP.NET Core

Oxpecker.Htmx

HTMX support for Oxpecker.ViewEngine

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.0.1 122 12/21/2024
1.0.0 823 11/19/2024
0.15.2 576 11/6/2024
0.15.1 408 10/26/2024
0.15.0 146 10/9/2024
0.14.1 95 10/8/2024
0.14.0 433 8/30/2024
0.13.1 2,204 8/23/2024
0.13.0 157 8/22/2024
0.12.0 492 8/13/2024
0.11.0 93 8/5/2024
0.10.2 174 7/24/2024
0.10.1 107 7/23/2024
0.10.0 311 7/17/2024
0.9.0 127 7/16/2024
0.8.0 120 6/18/2024
0.7.2 1,159 5/8/2024
0.7.1 133 4/29/2024
0.7.0 860 3/5/2024
0.6.0 137 3/3/2024
0.5.0 232 2/29/2024
0.4.0 157 2/21/2024
0.3.0 130 2/15/2024
0.2.0 296 1/24/2024
0.1.0 148 1/19/2024

Added explicit flush when rendering to Stream and TextWriter