d10518bbf609cbe13ea8379387830f1470757567 — Timur Ismagilov a month ago 0e5fd60
Write Boilerplate.md, explaining the views' boilerplate
1 files changed, 85 insertions(+), 0 deletions(-)

A Boilerplate.md
A Boilerplate.md => Boilerplate.md +85 -0
@@ 0,0 1,85 @@
# Boilerplate in Mycorrhiza codebase

Being programmed by Go, mostly by Bouncepaw, the codebase contains a lot of boilerplate. This document is an attempt to describe how it is done.

## Modules

Mycorrhiza is arranged in quite many packages. They are thematic. For example, package `backlinks` has all things backlinks, including the storage, the views, and exported functions (not many, ideally). Such packages can be called modules, if you want.

## Views

Views are the biggest source of similar code. Before the transition from QTPL to Go's standard templates, this boilerplate energy was split differently, but was not instantly obvious. The current approach does not really introduce new boilerplate energy, but it does focus it, resulting in actual boilerplate. I hope you get the idea.

All related views are part of one module.

Views come in multiple parts.

The first part is the template itself. Call template files like that: `view_user_list.html`, prefixed with `view_`. The boilerplate is as follows.

{{define "title"}}{{end}}
{{define "body"}}

More often than not, you will want to make template `title` a different template in the same file. See existing files for inspiration.

The code that makes those templates runnable lies in one file. This is the second part. It contains the following:.

The Russian translation is a `string` variable called `ruTranslation`; we currently have no other translations, but they are to be called like `frTranslation`, `eoTranslation`, et cetera.

var (
	ruTranslation = `
{{define "one thing"}}...{{end}}
{{define "other thing"}}...{{end}}

Chains are collection of different language variants of the same template. Declare them and then assign them in a function, which you call somewhere (not just `init`!).

var (
	ruTranslation              = `...`
	chainStuff, chainAddStuff viewutil.Chain

func initViews() {
	chainStuffs = viewutil.CopyEnRuWith(fs, "view_stuff.html", ruTranslation)
	chainAddStuff = viewutil.CopyEnRuWith(fs, "view_add_stuff.html", ruTranslation)

Then every view has a runner and its own datatype.


type dataStuff struct {
	StuffName string

func viewStuff(meta viewutil.Meta, stuffName string) {
	viewutil.ExecutePage(meta, chainStuffs, dataUserList{
		BaseData: &viewutil.BaseData{},
		StuffName: stuffName,

Sometimes, two datatypes of different views are the same, it is ok to just share one, but name it so that it mentions both.

Avoid any logic in those runners. Keep them as boilerplate as they are. You rarely need to fill the `BaseData` field. Do it if you need to. If you don't, `viewutil.ExecutePage` will do its best to guess. We name the fields with capital letters.

### Troubleshooting

* Declared the chains?
* Assigned the chains?
* Assigned the chains, sure?
* Used the correct data type?
* `*viewutil.BaseData` is there?
* Used the correct chain?
\ No newline at end of file