User:FrozenPlum: Difference between revisions
Content added Content deleted
imported>FrozenPlum mNo edit summary |
imported>FrozenPlum mNo edit summary |
||
Line 4:
For whatever reason, it seems like both Variabls and Loops extension (plus string functions enabled in ManageWiki for parser functions) are needed for only 2 templates... still unclear to me why those two have variables together in one of the 2 templates, I haven't looked closely at it. Since the future of variables extension is in question, probably it's just best to split these into separate templates, it's not a hardship to remember which would use what template
* Template:DPL parameter - for linking to a parameter (also linked to current DPL syntax template where the global vars are declared).
* Template:DPL syntax - for displaying variations on <code>mode=<i>modename</i></code>
** Am considering replacing with <code><nowiki>{{syntax|text{{=}}value}}</nowiki></code>
<!--{{dpl3|count}}-->
<!--
<includeonly><span id="{{{1|}}}">{{{2|}}}</span></includeonly><noinclude>
<templatedata>
{
"params": {
"1": {
"label": "Anchor Text (must be lowercase!)",
"description": "Enter anchor text (all lowercase)",
"type": "string",
"default": "purple",
"required": true
},
"2": {
"label": "Text to display beside anchor (optional)",
"description": "Enter the word or words to anchor to, note that spaces must be replaced by underscores, though dashes and colons can be used.",
"example": "mode",
"type": "string"
}
},
"description": "Creates a span with an ID to be used as a bookmark/named anchor by wrapping the content in a span with an id whose anchor text is whatever you set it to be. Then, you can link to it by using Pagename#anchorname\". Note: Anchor text is intentionally lowercase so it can never clash with existing Mediawiki anchors (TOC) which always start with an uppercase letter. "
}
</templatedata>
[[Category:Technical templates]]
</noinclude>
-->
|
Revision as of 06:36, 27 March 2022
This is not my wiki, I'm just a Miraheze user helping to get some content moved over. Feel free to reach me on my Talk page.
Self Reminder
For whatever reason, it seems like both Variabls and Loops extension (plus string functions enabled in ManageWiki for parser functions) are needed for only 2 templates... still unclear to me why those two have variables together in one of the 2 templates, I haven't looked closely at it. Since the future of variables extension is in question, probably it's just best to split these into separate templates, it's not a hardship to remember which would use what template
- Template:DPL parameter - for linking to a parameter (also linked to current DPL syntax template where the global vars are declared).
- Template:DPL syntax - for displaying variations on
mode=modename
- Am considering replacing with
{{syntax|text{{=}}value}}
- Am considering replacing with