Module talk:WikiProject banner/Archive 13

This is an old revision of this page, as edited by Lowercase sigmabot III (talk | contribs) at 04:27, 9 October 2020 (Archiving 1 discussion(s) from Template talk:WPBannerMeta) (bot). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Latest comment: 5 years ago by Ahecht in topic Detecting conflicts in class values
Archive 10Archive 11Archive 12Archive 13Archive 14Archive 15Archive 16

Automatic |tf_n=yes based on |TF_n_XYZ?

If someone fills in |TF_n_XYZ= (e.g. |TF_n_QUALITY=), would it be sensible to automatically trigger |tf_n=? I feel as though if you're assigning a taskforce quality rating, that it's safe to presume that taskforce should be activated. This would be particularly helpful for the WP:RATER tool. Since any text in |tf_n= will activate the section, the template could just include the nested parameters:

|tf_n={{yesno|{{{tf 4|{{{TF_n_LINK|{{{TF_n_NAME|{{{TF_n_NESTED|{{{TF_n_IMAGE|{{{TF_n_TEXT|{{{TF_n_QUALITY|{{{TF_n_MAIN_CAT|¬}}}}}}}}}}}}}}}}}}}}}}}}|yes|¬=¬}}

Thoughts? T.Shafee(Evo&Evo)talk 12:24, 1 May 2020 (UTC)

|TF_n_QUALITY= is set at the project template, but the |tf_n= is set at each article. The quality is just inherited from the main quality rating of that article; it is not specified for each task force. — Martin (MSGJ · talk) 07:44, 2 May 2020 (UTC)
@Evolution and evolvability: just wondering if my answer made any sense? — Martin (MSGJ · talk) 08:10, 5 May 2020 (UTC)
@MSGJ:. Woops, I meant to use Template:TF n IMP rather than |TF_n_QUALITY= as the example. Because currently, if Template:TF n isn't filled in, the template will ignore Template:TF n IMP. The template I'm working on is {{WikiProject_Molecular_Biology}}.
Example: {{WikiProject Molecular Biology |class=Stub |importance=Low |RNA-imp=high |MCB-imp=low}} returns:
 Molecular Biology Stub‑class Low‑importance
 This article is within the scope of WikiProject Molecular Biology, a collaborative effort to improve the coverage of molecular biology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
StubThis article has been rated as Stub-class on Wikipedia's content assessment scale.
LowThis article has been rated as Low-importance on the project's importance scale.
but should really return:
 Molecular Biology: Genetics / Biophysics Stub‑class Low‑importance
 This article is within the scope of WikiProject Molecular Biology, a collaborative effort to improve the coverage of molecular biology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
StubThis article has been rated as Stub-class on Wikipedia's content assessment scale.
LowThis article has been rated as Low-importance on the project's importance scale.
 
This article is supported by the Genetics task force (assessed as Low-importance).
 
This article is within the scope of the Biophysics task force, a task force which is currently considered to be inactive.
So the query is more about whether we can automatically assume |TF_n= is yes if any of the |TF_n_XYZ= parameters are filled. T.Shafee(Evo&Evo)talk 12:26, 5 May 2020 (UTC)
Ah, I understand your point now. Typically the only taskforce parameter that is set at the article level is the importance. So you are saying that if |biophysics-imp= is set to any value, then we should assume that |biophysics=yes? That would be fairly simple to implement. Are there any possible side effects of doing this? What if |biophysics-imp=cheesecake, i.e. an unrecognised value - should that trigger the taskforce as well? — Martin (MSGJ · talk) 13:38, 5 May 2020 (UTC)
On this matter, I occasionally see a parameter pair compressed into a single one. Take for instance Talk:László Szőcs - here, the {{WikiProject Football}} has |variants=mid which is not-quite invalid - it is treated as if it were |variants=yes but I suspect that the intention was |variants=yes|variants-importance=mid. --Redrose64 🌹 (talk) 20:51, 13 May 2020 (UTC)
I've not need that before, but it is efficient. Currently this is not recognised by the template, but it might be logical to make the taskforce importance default to the value of the taskforce activiation parameter? — Martin (MSGJ · talk) 06:18, 14 May 2020 (UTC)

Protected edit request on 19 May 2020

Please change Template:WPBannerMeta/core to Template:WPBannerMeta/core/sandbox (+protection template) diff. This change makes it so that the JS for collapsible is initialized slightly sooner and bypasses the collapsible to mw-collapsible proxy wrapper of en.wp. —TheDJ (talkcontribs) 08:31, 19 May 2020 (UTC)

I put a test on Template:WPBannerMeta/testcases. The alignment is slightly different in the new version, but it is not an issue. — Martin (MSGJ · talk) 08:42, 20 May 2020 (UTC)
  Done no other comments so I have made the change. If the alignment change is worrying anyone we can revert/discuss — Martin (MSGJ · talk) 11:16, 22 May 2020 (UTC)

Detecting conflicts in class values

Is there a way to identify conflicts between a page's assigned class value and what would otherwise be automatically detected? E.g., a redirect or a page in the Category namespace tagged as stub-class. --Paul_012 (talk) 23:58, 9 March 2020 (UTC)

Not currently, but it would be simple enough to code on a particular project's banner — Martin (MSGJ · talk) 21:47, 10 March 2020 (UTC)
Thanks. It's not needed so much that I'd ask for an actual implementation; just something that I thought would be nice to have. --Paul_012 (talk) 14:54, 12 March 2020 (UTC)
We've only used automatic detection of a page's class value if no class is defined. (If the class is defined then this will always be used.) I think this is the right approach in general, but any project can change this default behaviour by using a custom class mask. — Martin (MSGJ · talk) 23:03, 5 May 2020 (UTC)
@MSGJ: There probably are a few other cases where it might be useful to do automatic detection. For example, if an article is in mainspace but is tagged as "Draft class", it certainly means that whoever moved it to mainspace forgot to remove that it was a draft, and it should be treated as if the class were left undefined. --Ahecht (TALK
PAGE
) 21:30, 31 May 2020 (UTC)