Some possibilities for linking to more relevant help pages when creating Implementations (or other objects in the future)

No, I don't think we want to do anything else here. It should be possible to have a list of monolingual texts with repeated languages, if that's out of the context of a Multilingual string.

The concurrency errors given by the stampede of renderer function calls at once is fixed.
Thanks @99of9, I'll be closing this task now.

Not to close this.
Things marked as "Digital garden" are potential design ideas for the future.

This is old, and not a bug but a feature!!

While this is structurally possible, it does not happen and there's no plan for it to be a supported use case. Marking this as declined.

@DVrandecic, This is by design: no arbitrary texts can remain in the field, only valid selections.

Activation/deactivation of "Apply changes" button has been reworked and fixed since then.
@Etonkovidova could you maybe revisit this issue and see if you are able to replicate the behavior that you reported?

This now works well, yeah. Here's a list of lists of strings:

IS this still relevant now we have renderers and parsers @DVrandecic

Errors on connecting point at Diff\Comparer\StrictComparer missing

Incremental assignment of zids successfully jumped:

• from Z30009 https://www.wikifunctions.org/wiki/Z30009?uselang=en&action=history
• to Z30028 https://www.wikifunctions.org/wiki/Z30028?uselang=en&action=history

Thanks!
Regarding the must haves:

A couple of checks

• Oldid link to non-valid object doesn't show php error anymore https://www.wikifunctions.org/wiki/Z19588?uselang=en&oldid=135974
• Creation of the not-wellformed error is unavoidable, the structure is valid, but the resolving type of function calls don't match the keys. This is okay and unavoidable with current UI.

Performance is improved now. However, this page could do with a redesign.
However, this task is reg. performance issues which are now solved. Closing

Agreed. Closing

Closing. zfunctions.js: fetchImplementations and fetchTests are tested.

Yes this has been resolved for some time now, thanks for flagging!

@DSmit-WMF Not sure about the "external link" icon used here, it doesn't give any information about where exactly is this link taking you to.

some examples:

For manual testing (read/write, inside a composition), use:

For manual testing (read/write, out of composition context), use:

Thanks!
We show this notice message in converter pages (e.g. https://www.wikifunctions.org/wiki/Special:CreateObject?zid=Z46)

Checked in production.

After discussing with @cmassaro about current Ajv status, here's what I think:

• We should close this.
• We should definitely audit Ajv remains and make sure that unused things are removed, and if Ajv needs to remain for some reason, make it properly documented. This is not urgent and can be addressed in a future fixit week. Added: T411110: Investigate schemata/orchestrator remains of Ajv and schema usage and delete unused features

Waiting to verify in production in ~a week or so, when the zid pointer reaches Z30010 and jumps automatically to Z30028.

Checked correct behavior!

error_types.yml looks like its used for Ajv structural validation, but I'm not sure when we are using this, and how are these descriptors being used.
errors.js has the error zid constants that are used from function-orchestrator and function-evaluator utilities.
ZErrorTypeRegistry has the error zid constants that are used from wikilambda utilities

@DSmit-WMF this is quite an ancient task, but you can try replicate the "Z503/no connected implementation" error if you disable all implementations from a function (locally) and then try to run it a composition using it.
The current view of this is quite different:

No, that's not the case.