Template talk:In use
![]() | Template:In use 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 template-protected}} to notify an administrator or template editor 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. |
This is the talk page for discussing improvements to the In use template. |
|
![]() | This template was nominated for deletion. Please review the prior discussions if you are considering re-nomination:
|
|
|||
This page has archives. Sections older than 180 days may be auto-archived by Lowercase sigmabot III if there are more than 4. |
Edit request 28 May 2024
[edit]![]() | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
Add a =reason
param to provide explanation why the in use parameter is being used on the page. Qwerty284651 (talk) 13:46, 28 May 2024 (UTC)
Not done: please make your requested changes to the template's sandbox first; see WP:TESTCASES. * Pppery * it has begun... 03:14, 30 May 2024 (UTC)
Template-protected edit request on 18 July 2024 unnatural wording
[edit]![]() | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
− | for a | + | for a little while |
To my ear, "short while" sounds wrong. It is missing from Wiktionary. According to Google Ngrams, the usage of "little while" is more than 4 times more common than "short while" and "short while" was even rarer historically: https://books.google.com/ngrams/graph?content=for+a+little+while%2Cfor+a+short+while&year_start=1700&year_end=2019&corpus=en-2019&smoothing=3 . {{in use section}} needs the same fix. 174.92.25.207 (talk) 07:43, 18 July 2024 (UTC)
Completed. P.I. Ellsworth , ed. put'er there 18:23, 18 July 2024 (UTC)
Edit request 2 September 2025
[edit]![]() | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
Replace with {{In use/sandbox}}, which has a few minor improvements and no linter errors:
- "please" was used 3 times and many terms were repeated often
- it didn't use standard pb, which is used for templates with more than one paragraph
- clarify purge link (wasn't even grammatically correct) and put important timestamp info first
it's mainly a copyedit, nothing else changed. — Preceding unsigned comment added by FaviFake (talk • contribs)
- It appears that the rendering will change if
|1=
and|2=
are used. Are there testcases? – Jonesey95 (talk) 05:55, 2 September 2025 (UTC)- Jonesey95 There wasn't a change in functionality, only in the wording used; I've now created them: {{In use/testcases}} FaviFake (talk) 07:37, 2 September 2025 (UTC)
Done. – Jonesey95 (talk) 13:07, 2 September 2025 (UTC)
- Jonesey95 There wasn't a change in functionality, only in the wording used; I've now created them: {{In use/testcases}} FaviFake (talk) 07:37, 2 September 2025 (UTC)
Merging the underlying code of In use and GOCEinuse
[edit]The templates {{In use}} and {{GOCEinuse}} are based on the same underlying code, but {{In use}} has been improved a lot while {{GOCEinuse}} has largely remained the same, with some small changes to the text. To help maintenance of both templates, I propose we merge them into one.
Nothing will change if someone uses {{In use}}
alone, but if someone uses {{In use|GOCE=any value}}
, then the template will output almost the exact same template as {{GOCEinuse}}. Except that now there's an added benefit: improving one codebase will improve both templates.
You can check it out at {{GOCEinuse/testcases}}, since I've also rewritten {{GOCEinuse/sandbox}} (now it's simply a wrapper for {{In use/sandbox}}). Again, it would output almost the same message (I've also incorporated some very minor improvements into the GOCE version of "in use" which benefit both).
It works as tested in the appropriately modified testcases, and has no linter errors. I don't see a reason to keep them separate if the output can remain the same and is still so similar between the two. Thoughts? FaviFake (talk) 15:03, 28 September 2025 (UTC)