Jump to content

Wikifunctions:Feature petitions

From Wikifunctions

WF:FP redirects here. For compositions, which use the functional programming paradigm, see WF:How to create implementations#Compositions. For other FP languages, see WF:Rosetta.

This page is for users to petition requested features to the Abstract Wikipedia team and for the Abstract Wikipedia to gauge community consensus and priorities. To add your signature to a proposal, simply add # Any additional comments ~~~~ on a new line after a proposal. To add a new proposal, add ===Brief name, one sentence or so.=== to the bottom.

Proposals

New Types

Main page: WF:Type proposals

Partial functions/currying

Tracked in Phabricator:
Task T386422
  1. Feeglgeef (talk) 23:34, 27 March 2025 (UTC)reply
    • CMassaro (WMF) said There shouldn't be any issue from the backend's perspective. It sounds like a UI problem.
  2. Support Support PLEASE having to nest n-ary apply is killing me. YoshiRulz (talk) 14:29, 15 July 2026 (UTC)reply

N-argument apply/reduce/map

  1. 99of9 (talk) 00:25, 28 March 2025 (UTC)reply

For implementations and testers, show the associated function in Recent Changes (etc)

Feature summary: See a link to the associated function when there is a link to an implementation or a test, especially in Recent Changes and Special:ListObjectsByType)

Support Support as proposer GrounderUK (talk) 09:09, 30 March 2025 (UTC)reply

Return string values in a container that supports Copy and (optionally) makes non-display characters visible

Support Support as proposer GrounderUK (talk) 09:09, 30 March 2025 (UTC)reply

Provide details of result validation

Feature summary: The “Details” for a Test case should include (as a minimum) the Implementation used by the Function specified for the “result validation”.

Support Support as proposer GrounderUK (talk) 09:09, 30 March 2025 (UTC)reply

Improve access by functions to Persistent object labels (and other keys)

Support Support as proposer GrounderUK (talk) 09:09, 30 March 2025 (UTC)reply

Structured data/documentation

Weak Support Support since I suspect the workaround of {{Function documentation}}/{{Type documentation}}, in conjunction with Wikidata, will be sufficient. IIRC there are systems which parse the parameters in a Wikitext template call, should anyone want it machine-readable. YoshiRulz (talk) 07:55, 13 July 2026 (UTC)reply

Visually distinguish Wikidata items from properties

This call shows the problem: it echoes a Z6091, a Z6001, a Z6094, and a Z6004. They appear identical because the same icon is used, and their English labels are the same. A more realistic example is a composition like Z31134, with some items and some properties mixed in with a wall of text.

Support Support as proposer. YoshiRulz (talk) 14:12, 15 July 2026 (UTC)reply
I wrote some hacky CSS as a workaround. YoshiRulz (talk) 14:12, 15 July 2026 (UTC)reply