Wikifunctions:Request for cleanup

There are a number of objects where the development team is asking the community to help them in cleaning up the objects. Partially it is because we don't have the ability to do it ourselves (e.g. it involves labels and descriptions in languages we don't speak), partially it is because we want to reduce our usage of rights that should be firmly located with the community. Also, sometimes it is a judgement call we don't feel completely comfortable with making it given that our role.

Feel free to extend this page with further calls.

Duplicated objects

• throw error (Z28154): should be deprecated in favor of the built-in function for the same purpose Throw Error (Z851), and its uses replaced with calls to Throw Error (Z851):
  • intro for year functions (Z20896)
  • throw if not of lang else run, composition (Z21237)
  • 1st Lexeme from item reference, lang. composition (Z22700)
  • first Lexeme from item ref. and lang. comp:1st Obj (Z23222)
  • validate Rational number, composition (Z23279)
  • best lexeme for Wikidata item, Comp (Z27335)
  • Unlabelled (Z28162)
  • get nth element, recursive comp, with error (Z28172)
  • Item 2: head of tail composition, with error (Z28173)
  • Unlabelled (Z28234)
  • function passed is throw error, return void (Z28251)
  • apply unless Throw error, composition (Z28252)

Empty language references

Context: T400271

Currently all issues fixed.

Wrongly configured function calls

Context: T398457

Quick check

• [object plural]+ki composition (Z12158): "first string" should be an argument reference to "nominative case singular", not a function call where function is "nominative case singular".

Done Special:Diff/219277 --GrounderUK (talk) 10:13, 20 September 2025 (UTC)

• is Natural number, recursive composition (Z15828): extra function call nesting. In the "If" function call inside the "then" statement, the "condition" should be a function call to "is Natural number", but instead it is a function call to a function call.

Done Special:Diff/219089 GrounderUK (talk) 09:17, 20 September 2025 (UTC)}}

• [dated] Korean -eul composition (Z18404): extra function call nesting. In the first argument to the Z886 function, the second item is defined by an "If" function; the condition to this "If" should be a function call to Z12778, but instead it is a function call to a function call. This is using deprecated functions, so probably Z886 should be replaced with Z22693
• Z13059: extra function call nesting. The "function" argument of "apply" should be a function call to "compose", but instead is a function call to a function call.

The function tested is not viable, as defined. Perhaps it might return a Function call (Z7), but it has no argument for the resultant call’s arguments. In any event, it would end up as a special case of apply list of functions (Z13351) (at least, that’s how I might implement it).--GrounderUK (talk) 09:12, 20 September 2025 (UTC)

I’ve removed the outermost Function call (Z7) anyway . This also discards the lowercase String (Z6) argument and the conversion to uppercase (Z10018). GrounderUK (talk) 09:47, 20 September 2025 (UTC)

• exponential factorial by composition (Z18271): extra function call nesting. In the "else"."value"."power"."value" should be defined by a function call to exponential factorial, but instead it is defined by a function call to a function call.

Done Special:Diff/219266 GrounderUK (talk) 09:12, 20 September 2025 (UTC)}}

• wrapper around defining role sentence (Z28110): badly formed Argument reference/Z18. This composition calls defining role sentence in English (Z28026) passing it down its four arguments. However, the second one (argument "role", for Z28026K2) is not wellformed. Looking into the raw object we see that the value of Z28026K2 is { "Z1K1": "Z18", "Z18K1": { "Z1K1": "Z18", "Z6K1": "Z28109K2", "Z18K1": "" } } where it should be { "Z1K1": "Z18", "Z18K1": "Z28109K2" }. Editing the object and changing the mode of "role" from "Argument reference" to something else, and back to "Argument reference", then selecting "role" should reset it to a valid format.

Done GrounderUK (talk) 19:08, 16 October 2025 (UTC)

Long names and descriptions

We have introduced restrictions on the length of names and descriptions. But there are a few that are too long and need cleanup. A static list is available here: Long labels and descriptions.

Functions that don't seem to make sense

These are Functions we encountered and are asking for a review.

Currently no open issues.