Template talk:Infobox weather event

(Redirected from Template talk:Infobox weather event/FMS)
Latest comment: 1 month ago by Nikkimaria in topic "Damages" should be "damage"

79.1% Infobox weather event adoption (2200 / 2783) as of 00:45, 9 May 2024 (UTC)

   

Infobox for cloud tops

edit

There is no section or parameter for maximum cloud top height. While this isn't a commonly used parameter recorded in secondary sources, cloud top heights are occasionally recorded when it's an exceptionally high value, and it can be useful for describing the intensity of supercells and some cyclones specifically, so I am requesting it be considered to be added. GeorgeMemulous (talk) GeorgeMemulous (talk) 14:03, 21 August 2024 (UTC)Reply

"Damages" should be "damage"

edit

"Damages" as used here is incorrect and should be replaced with "damage". See WP:DAMAGES. I propose that "damage" be added as an alias for the "damages" parameter and then we can replace all usage in articles with it, then finally delete the "damages" parameter. Note that other infoboxes already use "damage" instead, e.g. Template:Infobox public transit accident. Un assiolo (talk) 14:09, 11 September 2024 (UTC)Reply

@Un assiolo: There's no reason to change anything. Damage is what is stated within the infobox when both damage and damages are used. Noah, BSBATalk 15:59, 11 September 2024 (UTC)Reply
My mistake. It seems both damage and damages are allowed, and they both show up as "Damage", so we're most of the way there. We just need to deprecate damages in favour of damage. It needs to be deprecated because it gives the impression that "damages" is correct. I think the parameter can be replaced in articles where it is used by a bot, and then we just remove the functionality from the template once that's done. I'm going to update the documentation to replace "damages" with "damage". --Un assiolo (talk) 17:20, 11 September 2024 (UTC)Reply
There is no such need; it harms nothing to have an alias available in the code. Nikkimaria (talk) 04:31, 12 September 2024 (UTC)Reply