 | This template was considered for deletion on 24 October 2024. The result of the discussion was "keep". |
 | This template does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||
| ||||||||
Division of labour
editDoesn't this template do exactly the same thing as {{about}} with an empty first parameter? I.e. {{For multi|use|article}} produces the same result as {{About||use|article}}. – Uanfala (talk) 14:59, 24 July 2021 (UTC)
- @Uanfala Yes as they use the exact same Lua module function to produce the "For..., see..." list. I made this template because using {{About}} with an empty first parameter seems hacky and I could see it potentially causing some confusion. I also plan on replacing uses of {{For2}} that would work better with a template like this with this template. – BrandonXLF (talk) 21:27, 24 July 2021 (UTC)
- Yeah, I agree that the trick with {{about}} is hacky. But, on the other hand, I don't think creating a new template is the optimal solution as it doesn't seem to help in reducing the complexity of the hatnotes templates ecosystem. At the very least, the name for-multi could conceivably apply to both templates, as they can both receive multiple arguments. I'm wondering if there isn't a neat way to fold this functionality into the existing template. I think it's more intuitive for that to be the default behaviour of {{for}}, and what it currently does – treating most arguments as articles – to be triggered specifically. For example, it doesn't seem to make any use of an empty first argument, so that could serve as a switch (though that's getting hacky again). Anyway, that's just me brainstorming, I don't know how realistic any of these suggestions are. – Uanfala (talk) 11:56, 25 July 2021 (UTC)
- I do agree that it would be nice to integrate this functionality into the existing template, but I don't see any practical way to do it. Even if it's more intuitive for the behavior of this template to be the behavior of that template, changing the functionality of {{for}} seems like it is out of the question as it is heavily used (although only 3018 uses use 3 or more parameters [1]) and editors are use to the way it currently works (which might be less of an issue than I think it is?). Having a switch doesn't seem like a good idea because completely changing how a template works with a single parameter seems like it could cause issues if someone doesn't notice the flag or if they aren't aware of how the flag changes the behavior of the template, especially since the flag changes how the template treats parameters. – BrandonXLF (talk) 07:39, 26 July 2021 (UTC)
- Some other possible solutions that could maybe work are using CSS to condense multiple {{For}} templates in a row into one line (maybe with a wrapper template enclosing all the templates) or using a special character (like a semicolon or comma) in the article parameters to seperate page names, so multiple pages can be given for a use without having to use additional parameters. – BrandonXLF (talk) 07:54, 26 July 2021 (UTC)
- I do agree that it would be nice to integrate this functionality into the existing template, but I don't see any practical way to do it. Even if it's more intuitive for the behavior of this template to be the behavior of that template, changing the functionality of {{for}} seems like it is out of the question as it is heavily used (although only 3018 uses use 3 or more parameters [1]) and editors are use to the way it currently works (which might be less of an issue than I think it is?). Having a switch doesn't seem like a good idea because completely changing how a template works with a single parameter seems like it could cause issues if someone doesn't notice the flag or if they aren't aware of how the flag changes the behavior of the template, especially since the flag changes how the template treats parameters. – BrandonXLF (talk) 07:39, 26 July 2021 (UTC)
- Yeah, I agree that the trick with {{about}} is hacky. But, on the other hand, I don't think creating a new template is the optimal solution as it doesn't seem to help in reducing the complexity of the hatnotes templates ecosystem. At the very least, the name for-multi could conceivably apply to both templates, as they can both receive multiple arguments. I'm wondering if there isn't a neat way to fold this functionality into the existing template. I think it's more intuitive for that to be the default behaviour of {{for}}, and what it currently does – treating most arguments as articles – to be triggered specifically. For example, it doesn't seem to make any use of an empty first argument, so that could serve as a switch (though that's getting hacky again). Anyway, that's just me brainstorming, I don't know how realistic any of these suggestions are. – Uanfala (talk) 11:56, 25 July 2021 (UTC)
Example with two alternative topics
editI suggest adding a simple example of what {{For-multi|UseA|ArticleA|UseB|ArticleB}} will do in the template instructions. I don't see that in the current instructions. That seems like an important and straightforward use that could be used often. The need for the {{For2}} template is currently under discussion here. Having this example of how this template can be used in this simple scenario could help show that it can be used for that purpose. —???BarrelProof (talk) 18:56, 23 August 2023 (UTC)
#ff abbreviation
editHere is included a link to the Oxford Advanced Learner's Dictionary to explain usage of "#ff" in the TemplateData section for those editors who are unfamiliar. P.I. Ellsworth?, ed. put'er there 17:20, 26 February 2024 (UTC)
Selfref
editThis doesn't seem to support |selfref=y like {{for}} does. If so, would this be simple to fix? jlwoodwa (talk) 20:30, 15 May 2024 (UTC)