Template:Para

From TF Library

Jump to: navigation, search

Contents

Usage

This template is for giving examples of template parameter source code (useful in template documentation and talk page discussions of template code). It must have one or two parameters itself. The first is the name of the example parameter to display (this may be empty, but it must be present), and the second (optional) one is a value for the first example parameter, or (if the first

  1. REDIRECT Delete 24 parameter is empty) an unnamed example parameter.

Examples

  1.   
  2. REDIRECT Delete 24
    renders as
    == Usage ==

This template is for giving examples of template parameter source code (useful in template documentation and talk page discussions of template code). It must have one or two parameters itself. The first is the name of the example parameter to display (this may be empty, but it must be present), and the second (optional) one is a value for the first example parameter, or (if the first

  1. REDIRECT Delete 24 parameter is empty) an unnamed example parameter.

Examples

  1.   
  2. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para
  3.   
  4. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para
  5.   
  6. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para
    (for unnamed parameters in the example code; note the empty first parameter in the
  7. REDIRECT Delete 24 template)
  8.   
  9. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para

When using literal, pre-specified values, simply provide the value (appearance as in example 3). When illustrating hypothetical, variable or user-definable values, use <var>value</var> (appearance as in example 2), and the same should be done for non-literal, example parameters (as in example 4).

  1.   
  2. REDIRECT Delete 24
    renders as
    == Usage ==

This template is for giving examples of template parameter source code (useful in template documentation and talk page discussions of template code). It must have one or two parameters itself. The first is the name of the example parameter to display (this may be empty, but it must be present), and the second (optional) one is a value for the first example parameter, or (if the first

  1. REDIRECT Delete 24 parameter is empty) an unnamed example parameter.

Examples

  1.   
  2. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para
  3.   
  4. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para
  5.   
  6. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para
    (for unnamed parameters in the example code; note the empty first parameter in the
  7. REDIRECT Delete 24 template)
  8.   
  9. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para

When using literal, pre-specified values, simply provide the value (appearance as in example 3). When illustrating hypothetical, variable or user-definable values, use <var>value</var> (appearance as in example 2), and the same should be done for non-literal, example parameters (as in example 4).

  1.   
  2. REDIRECT Delete 24
    renders as
    == Usage ==

This template is for giving examples of template parameter source code (useful in template documentation and talk page discussions of template code). It must have one or two parameters itself. The first is the name of the example parameter to display (this may be empty, but it must be present), and the second (optional) one is a value for the first example parameter, or (if the first

  1. REDIRECT Delete 24 parameter is empty) an unnamed example parameter.

Examples

  1.   
  2. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para
  3.   
  4. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para
  5.   
  6. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para
    (for unnamed parameters in the example code; note the empty first parameter in the
  7. REDIRECT Delete 24 template)
  8.   
  9. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para

When using literal, pre-specified values, simply provide the value (appearance as in example 3). When illustrating hypothetical, variable or user-definable values, use <var>value</var> (appearance as in example 2), and the same should be done for non-literal, example parameters (as in example 4).

  1. (for unnamed parameters in the example code; note the empty first parameter in the
  2. REDIRECT Delete 24 template)
  3.   
  4. REDIRECT Delete 24
    renders as
    == Usage ==

This template is for giving examples of template parameter source code (useful in template documentation and talk page discussions of template code). It must have one or two parameters itself. The first is the name of the example parameter to display (this may be empty, but it must be present), and the second (optional) one is a value for the first example parameter, or (if the first

  1. REDIRECT Delete 24 parameter is empty) an unnamed example parameter.

Examples

  1.   
  2. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para
  3.   
  4. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para
  5.   
  6. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para
    (for unnamed parameters in the example code; note the empty first parameter in the
  7. REDIRECT Delete 24 template)
  8.   
  9. REDIRECT Delete 24
    renders as
    Template loop detected: Template:Para

When using literal, pre-specified values, simply provide the value (appearance as in example 3). When illustrating hypothetical, variable or user-definable values, use <var>value</var> (appearance as in example 2), and the same should be done for non-literal, example parameters (as in example 4).

When using literal, pre-specified values, simply provide the value (appearance as in example 3). When illustrating hypothetical, variable or user-definable values, use <var>value</var> (appearance as in example 2), and the same should be done for non-literal, example parameters (as in example 4).

Personal tools
TOOLBOX
LANGUAGES