Template:Drop/doc: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 9: | Line 9: | ||
}, | }, | ||
"description": { | "description": { | ||
"en-ca": "The source of the drop. Maximum 32 characters." | "en-ca": "The source of the drop. Maximum of 32 characters." | ||
}, | }, | ||
"example": { | "example": { | ||
| Line 22: | Line 22: | ||
}, | }, | ||
"description": { | "description": { | ||
"en-ca": "The label of the table the drop belongs to. | "en-ca": "The label of the table the drop belongs to. Maximum of 32 characters." | ||
}, | }, | ||
"example": { | "example": { | ||
Revision as of 15:51, 6 July 2025
No description.
| 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 |
Notes
- If used in a namespace, the store will fail with notice.
- If any invalid arguments are provided, 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.