DO NOT MERGE: pageTemplate for forms question

[chromy]

I was looking into converting the 'commands' pages (formGet) to use pageTemplate as done already by queryGet. This avoids every route having to apply the template itself.

I think I found the place where pageTemplate ought to be added. However I don't understand what the idiomatic way to thread a variable from earlier in the pipe is. @Lan2u @erkannt: any advice you have appreciated! XD

[erkannt]

Ah yes. That is always a fun one. Haven't found the solution. Depending on the surrounding context and what feels nice I'd go for one of three options:

• Encapsulate construction, rendering and pageTemplating into a new (local) pipe function so that user can be in scope for all steps of that pipe.
• Have imperative section above the pipe. Kind of like a let block in Elm. In this case that would be a little bit annoying due to the Option returned by getUserFromSession, so an early return might be needed.
• Have the pipe keep stuff from previous steps around, slowly building an object with ever more keys so that the user sticks around. This is where Do-Notation comes in.

Pragmatically I'd probably go for the first option. Zooming out I am wondering whether pageTemplate should even require a User. It is only used to toggle log-in/log-out in the navbar, however all of our pages apart from the log-in require the user to be logged in. At this point I'd suggest ripping out the requirement for User in the pageTemplate and that should remove the issue you encountered.