Template:Generic Pattern Adjacent Service Row: Difference between revisions
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|}}}}} | ||
| | |{{#switch: {{{choice|Must}}} | ||
| | |MAY | ||
|May | |May | ||
|may=optional | |may=optional[[May have adjacent service::{{{service|}}}|]] | ||
| | |#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
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= }}
The above documentation is transcluded from Template:Generic Pattern Adjacent Service Row/doc. (edit | history) Editors can experiment in this template's sandbox (create | mirror) and testcases (create) pages. Please add categories and interwikis to the /doc subpage. Subpages of this template. |