Template:Generic Pattern Adjacent Service Row: Difference between revisions

From OIAr
Jump to navigation Jump to search
(more robust switch)
(default specified as mandatory, simpler switch)
Line 1: Line 1:
<includeonly>
<includeonly>
|{{FriendlyPageLink|{{{service|}}}}}
|{{FriendlyPageLink|{{{service|}}}}}
|[[{{{choice|Must}}} have adjacent service::{{{service|}}}|]]{{#switch: {{{choice|Must}}}
|{{#switch: {{{choice|Must}}}
|Must
|MAY
|must=mandatory
|May
|May
|may=optional
|may=optional[[May have adjacent service::{{{service|}}}|]]
|undefined}}
|#default=mandatory[[Must have adjacent service::{{{service|}}}|]]}}
|{{#show: {{{service|}}} | ?Brief description}}
|{{#show: {{{service|}}} | ?Brief description}}
|{{{reason|not specified}}}
|{{{reason|not specified}}}

Revision as of 10:15, 18 July 2013

Template documentation

This template creates a single row in a table listing all Adjacent Services for a Generic Pattern. It takes the following, mandatory, named parameters:

  • service: must be the name of a page representing the adjacent Generic Service;
  • choice: the architect can specify if the adjacency of the Pattern Type is mandatory or optional, by using either the word "Must" or "May". If left empty, "Must" is assumed!
  • reason: here the architect will usually insert an explanatory text, describing the rationale for adjacency.

To use this template, cut and paste the following text:

{{Generic Pattern Adjacent Service Row
|service=
|choice=
|reason=
}}