This template was considered for deletion on 18 March 2021. The result of the discussion was "keep". |
Template:Template link is permanently
protected from editing because it is a
heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by
consensus, editors may use {{
edit protected}} to notify an administrator to make the requested edit. Usually, any contributor may edit the template's
documentation to add usage notes or
categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
Text has been copied to or from this page; see the list below. The source pages now serve to
provide attribution for the content in the destination pages and must not be deleted as long as the copies exist. For attribution and to access older versions of the copied text, please see the history links below.
|
|
||
This page has archives. Sections older than 14 days may be automatically archived by Lowercase sigmabot III when more than 3 sections are present. |
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Regarding some text in the /doc subpage:
I believe based on the grammar and spacing that it should be "<something> and <something> are not interchangeable"; as is it's very strange. Maybe the entire text following and including the colon should just be deleted?
Diff:
− | This is not true for all such visually confusing templates containing a possible 1/l mix-up | + | This is not true for all such visually confusing templates containing a possible 1/l mix-up. |
CharredShorthand ( talk) 08:50, 11 December 2022 (UTC)
a possible 1/l mix-up as they are not interchangeablebecause it makes explicit that you can't just sub in a 1 for an l in templates. Primefac ( talk) 09:38, 11 December 2022 (UTC)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Wrap the template's code within the "includeonly" tag. Grufo ( talk) 07:27, 15 July 2023 (UTC)
<includeonly>
makes the documentation page ugly. --
Grufo (
talk) 18:19, 15 July 2023 (UTC)
<includeonly>
tag was invented for a reason. As it is it just looks like a broken page. --
Grufo (
talk) 12:24, 17 July 2023 (UTC)
It shows the output of the template: It doesn't. This is the output of the template:
I seem to recall you have made this complaint in the past: If I did I honestly don't remember, but I wouldn't be surprised.
There is no reason to hide template output.Again, that is not the output, it is the source code. The fact that you appreciate the feeling of reconstructing in your mind how a template would look like by looking at its source code might not be a shared feeling among everyday users of this template. I, for example, on top of a documentation page prefer to see how a template looks like instead of seeing its source code. -- Grufo ( talk) 14:45, 17 July 2023 (UTC)
|1=
is not specified. That is often done on template pages. Maybe I misunderstand the objection. If you want examples, the documentation is the place to look for those. –
Jonesey95 (
talk) 21:55, 17 July 2023 (UTC)
The top of the page shows the actual output of the template when |1=
is not specified
: Is that a possible case? From what I read
in the TemplateData the |1=
parameter is required. So what you call “output” is technically
undefined behavior, which today manifests as the partial source code, tomorrow might manifest as an error message, or whatever. But since we live in the present, what we see today is the template's partial source code on top of its documentation page.That is often done on template pages: Years ago, probably. Today we have
<includeonly>...</includeonly>
, and more and more template documentations have the wisdom of showing as early as possible (possibly on top) the template at work – not the template during undefined behavior.|1=
is missing (which would be totally legit, since it is a required parameter): would you still be happy to have “Error: Template name is missing” on top of the documentation page? What information would that give you, given that at that stage you won't even know what parameter you will have to use to provide a template name? Will that be |1=
? Or will that be |tp=
or |template=
instead?This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Description of suggested change: Please add a nocat value, especially when adding this template adds the page into unintended categories. I couldn't give examples. Toadette ( Merry Christmas, and a happy new year) 15:02, 4 January 2024 (UTC)