Wikifunctions:Status
 | Abstract Wikipedia team staff primarily maintain this page's content. |
This page aims to give a reasonably current view on the current status of Wikifunctions. If something does not work, this page is a good first stop to check if that is a known issue.
This page is not the complete source of details. A more immediate view is the "Abstract Wikipedia" Phabricator board. This page just aims to provide a good and more easily understandable overview of major known issues and problems.
See Wikifunctions:Report a technical problem for details on how to report a bug or make a feature request.
Summary: This page is not complete. We don't plan to list every single user facing issue, but merely the main ones.
Prioritisation framework
This is the framework the development team use to make sure we're working on the important things for you.
| Level | Meaning | Timeliness | Areas of concern | Example |
|---|---|---|---|---|
| P0 | A critical concern in production that must be fixed immediately | Fix immediately. Drop everything. |
|
|
| P1 | The service is significantly limited, for a large number of users | Fix within a week. |
|
|
| P2 | The service is limited, for a smaller number of users | Fix within a month. |
|
|
| P3 | The service is imperfect, or could do better (including new feature requests) | Triage and set expectations. |
|
|
Is anything currently very broken?
- No current known P0 or P1 issues!
What are we working on this Quarter? (April–June 2025)
 | Updates on this Quarter's work, and the new Quarter's work to come, are first published in the community newsletter. |
Each Quarter, we set out in a Weekly Update our plans, and then report on how we're doing.
The current work plan, for April–June 2025, was published in 2025-04-05:
- (T390543) If we establish and meet performance standards, we can have confidence that rolling out Wikifunctions access to more wikis will not disrupt those wikis' experiences or colleagues' work
- (T390548) Establish an SLO for the Wikifunctions integration into Wikimedia projects' wikitext pages, to assure reader experience quality is maintained during roll-out
- (T390549) Implement Object and Wikidata entity caching mechanisms in the function-orchestrator to drive up user experienced performance when making function calls
- (T390550) Implement Object and Wikidata entity batching mechanisms in the function-orchestrator to drive up user experienced performance when making function calls and reduce load on production wikis
- (T390544) If we roll out Wikifunctions access to more Wikimedia wikis, we will see wider use to deliver content and learn how well it works with different languages and communities to address content gaps
- (T390551) Make embedded Wikifunctions available in at least five more Wikimedia projects, to learn from other languages and communities
- (T390552) Listen to feedback from the pilot Dagbani Wikipedia community and adapt features, so that we can identify blockers to further rollout, and increase value to editors and readers, and so help the community
- (T390545) Improve features related to the Wikifunctions integration, so that wiki editors can use Wikifunctions in articles with more confidence.
- (T390553) Support default values when fields are left blank for date inputs in the Wikifunctions integration so that editors can use it more simply
- (T390554) Show read-mode errors from the Wikifunctions integration inline rather than in a box, so that editors can be less disrupted when something is wrong
- (T390555) Show a preview of the function call result in the Wikifunctions integration dialog, so that editors can adjust their uses more swiftly
- (T390557) Display the local and cross-wiki pages on which a Function is used, so that Wikifunctions users can see the impact of their changes
- (T390546) Extend features to use Wikidata items more fluently, so that Wikifunctions editors can do more things and so address content gaps more readily.
- (T390558) Support a light-weight enum Type alternative in the Wikifunctions front-end and in the Wikifunctions integration so that editors can use them more easily
- (T390559) Extend support for Wikidata items to cover unitful values and other types, so that function creators can take advantage of more of the content features of Wikidata
- (T390560) Improve the performance in the Wikifunctions front-end, so that function creators and users can use complex and large Objects such as those from Wikidata without difficulty
- (T390547) Build plans in the Abstract Wikipedia team on how to address common concerns and proposed feature expansions, so that we can be prepared for taking this on in future.
- (T390561) Experiment with how we might support rich content as output, including in the Wikifunctions integration, so that we can see how to support future use cases. Develop a plan based on this.
- (T390563) Develop a plan for how we might support macro-languages like Chinese, so that we can see how to support them as groups in future
- (T390564) Discuss with the Wikifunctions community and others where we might host Abstract Content in the future, so that we can prepare for that work
On top of the above planned work, we'll also have some "essential work", where we respond to bug fixes and emergency situations following our standard protocols, aimed at reducing disruption for the Wikifunctions community and its users.
You can see our team's Phabricator board for the current Quarter for more detailed tracking of how things are going.
Longer-term plans
- These are issues that we hope to work on in the future, as part of the bigger plans for Wikifunctions and Abstract Wikipedia. We will prioritise between them based on your feedback and ideas.
Type creation is locked-down to staff
For now, we only support a limited number and nature of types, and creation is limited to only staff. There are a number of built-in functions, e.g. first element of a list, typed list, and many others, which are currently not well-supported for custom types, which we are looking at addressing. Generic types and generic functions require a bit of development and bug-fixing, and are not ready yet.
You cannot embed Wikifunctions calls in Wikipedia articles, Wiktionary entries, etc.
This is a vital part of helping communities get the benefit of Wikifunctions, as well as building towards the Abstract Wikipedia goal. We're currently working on this
Function pages don't show you where or how much they're used
This would be an important way for the Wikifunctions community to decide how to focus effort and warn users of changes, like how the GlobalUsage tool guides the Commons community.
Diffs are ugly, so it's hard to do vandalism patrolling or community moderation
For now, diffs "work" but shows ugly blobs of JSON rather than a nice, understandable, formatted result. We want an experience like Wikidata's or better.
Search is ugly, so it's a problem to find things
For now, the search "works" but shows ugly blobs of JSON rather than a nice, understandable, formatted result, and you can't filter by type of object (e.g. "show me only Implementations that match my search").
Note: You can include the required type’s reference (e.g. "Z14") prefixed by the literal "Z1K1:" (case insensitive) in your search. For example, "suffix z1k1:Z14" will tend to find Implementations containing the string "suffix" (because Functions and Test cases are unlikely to contain a string that is equivalent to "z1k1:Z14, whereas all Implementations contain "Z1K1": "Z14" in their JSON representations and this is equivalent to "z1k1:Z14").