README
¶
dp-renderer
A rendering library for Digital Publishing frontend microservices. dp-renderer contains templates, localisations and model structs that are core to all dp-frontend services.
dp-renderer is intended to be used instead of calling dp-frontend-renderer to generate HTML, which consequently means more explicit domain encapsulation of our frontend apps and the removal of a single point of failure within the DP frontend architecture.
Note: although the dp-frontend-renderer is deprecated there is a transition period where updates will be needed in dp-renderer and the dp-frontend-renderer. See the README on the dp-frontend-renderer for the migration status.
Installation
Other than dp-renderer itself, you will need a utility that can combine service-specific and dp-renderer assets. We currently use go-bindata for this process.
dp-renderer:go get github.com/ONSdigital/dp-renderer
You can specify a version of
dp-rendererby appending a commit ID or semantic version number to this command. E.g.,go get github.com/ONSdigital/dp-renderer@31d8704
go-bindata:go get github.com/kevinburke/go-bindata
Migrating from dp-frontend-renderer and dp-frontend-models to using dp-renderer
See the migration guide for step-by-step details.
Usage
Instantiation
Assuming you have go-bindata set up to generate the relevant asset helper functions, you can instantiate the renderer with a default client (in this case, the default client is unrolled).
rend := render.NewWithDefaultClient(asset.Asset, asset.AssetNames, cfg.PatternLibraryAssetsPath, cfg.SiteDomain)
You can also instantiate a Render struct without a default client by using New(). This requires a rendering client that fulfills the Renderer interface to be passed in as well.
rend := render.New(rendereringClient, patternLibPath, siteDomain)
Mapping data and building a page
When mapping data to a page model, you can use NewBasePageModel to instantiate a base page model with its PatternLibraryAssetsPath and SiteDomain properties auto-populated via the Render struct:
basePage := rendC.NewBasePageModel()
mappedPageData := mapper.CreateExamplePage(basePage)
In order to generate HTML from a page model and template, use BuildPage, passing in the ResponseWriter, mapped data, and the name of the template:
rend.BuildPage(w, mappedPageData, "name-of-template-file-without-extension")
If an error occurs during page build, either because of an incorrect template name or incorrect data mapping, dp-renderer will write an error via an errorResponse struct.
Contributing
See CONTRIBUTING for details.
License
Copyright © 2021, Office for National Statistics (https://www.ons.gov.uk)
Released under MIT license, see LICENSE for details.
Documentation
¶
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Render ¶
type Render struct {
PatternLibraryAssetsPath, SiteDomain string
// contains filtered or unexported fields
}
func New ¶
New returns a render struct and accepts any rendering client that satisfies the Renderer interface
func NewWithDefaultClient ¶
func NewWithDefaultClient(assetFn func(name string) ([]byte, error), assetNameFn func() []string, assetsPath, siteDomain string) *Render
NewWithDefaultClient returns a render struct with a default rendering client provided (default: unrolled/render)
func (*Render) BuildPage ¶
BuildPage resolves the rendering of a specific page with a given model and template name
func (*Render) NewBasePageModel ¶
NewBasePageModel wraps around the model package's NewPage function, but injects the assets path and site domain from the render struct. This is to negate the need for the caller to have to provide these values for every new page created in a frontend service
Source Files
Directories