Template:Drop/doc: Difference between revisions
(add name) |
(split rendering components to own page) |
||
(4 intermediate revisions by the same user not shown) | |||
Line 63: | Line 63: | ||
}, | }, | ||
"description": { | "description": { | ||
"en-ca": "The name of the item. | "en-ca": "The name of the item. Used for Template:Drop/Article." | ||
} | }, | ||
"example": { | |||
"en-ca": "Eternal Psychodrive/U+" | |||
}, | |||
"type": "string" | |||
}, | |||
"link": { | |||
"label": { | |||
"en-ca": "Link to Page" | |||
}, | |||
"description": { | |||
"en-ca": "The page of the item. Used for Template:Drop/Article. " | |||
}, | |||
"example": { | |||
"en-ca": "Eternal Psychodrive/U+" | |||
}, | |||
"type": "wiki-page-name", | |||
"suggested": true | |||
} | } | ||
}, | }, | ||
"description": "Template used for displaying and/or storing items and their drop locations in Cargo. | "description": "Template used for displaying and/or storing items and their drop locations in Cargo.", | ||
"paramOrder": [ | |||
"source", | |||
"table label", | |||
"item id", | |||
"tickets", | |||
"name", | |||
"link" | |||
], | |||
"format": "block" | |||
} | } | ||
</templatedata> | </templatedata> | ||
== Notes == | == Notes == | ||
* If used in a namespace, the store will fail with notice | * Calls [[Template:Drop/Article]]. | ||
* If used in a namespace, the store will fail with notice, superseding all other functionality. | |||
* If '''any''' arguments that would be passed to Cargo are invalid, the store will silently fail. | * If '''any''' arguments that would be passed to Cargo are invalid, the store will silently fail. | ||
** It is not known to me, at this time, if it is possible to make Cargo return an error if validation fails without duplicating the logic into the Drop template itself. As a stopgap, viewing page values will detail what fields are being sent to Cargo. | ** It is not known to me, at this time, if it is possible to make Cargo return an error if validation fails without duplicating the logic into the Drop template itself. As a stopgap, viewing page values will detail what fields are being sent to Cargo. | ||
* Additionally, if any stores are rejected on a page using this template, all subsequent stores (using this template?) on said page will automatically fail. | * Additionally, if any stores are rejected on a page using this template, all subsequent stores (using this template?) on said page will automatically fail. |
Latest revision as of 17:05, 6 July 2025
Template used for displaying and/or storing items and their drop locations in Cargo.
Parameter | Description | Type | Status | |
---|---|---|---|---|
source | source | no description | String | required |
table label | table label | no description
| String | required |
item id | item id | no description | String | required |
tickets | tickets | no description | Number | required |
name | name | no description | String | optional |
link | link | no description | Page name | suggested |
Notes
- Calls Template:Drop/Article.
- If used in a namespace, the store will fail with notice, superseding all other functionality.
- If any arguments that would be passed to Cargo are invalid, the store will silently fail.
- It is not known to me, at this time, if it is possible to make Cargo return an error if validation fails without duplicating the logic into the Drop template itself. As a stopgap, viewing page values will detail what fields are being sent to Cargo.
- Additionally, if any stores are rejected on a page using this template, all subsequent stores (using this template?) on said page will automatically fail.