Look at me, making a comment!

Evan You's position is that <script setup> and Composition API is the recommended pattern going forward, and that the Vue documentation will be updated to reflect that. Source: https://github.com/vuejs/rfcs/discussions/378#discussioncomment-1158805

I'd like to prioritize this discussion, so that the description is ready for working on the new designs.

I'd like to push back on this one. Using a strongly typed functional language as a base, null should not be an allowed input to any function, since it does not match a ZType. I'd suggest that we catch null as a bad argument and throw a Z5 rather than gracefully fail within the builtin itself.

How often does the orchestrator get redeployed? The fix is up and working for me locally, not sure what's happening on NWL now.

Looks like this may be caused by a failure to dereference Z18 in the orchestrator. Looking into it.

It appears like search is correctly returning ZObjects. Is there further functionality that we wanted to integrate here?

Is this reliant on T275093? Or is that task complete and we're ready to begin work on this one?

Do we still want to do this? Or should we mark as resolved for now and wait for Aishwarya's designs?

Is this a duplicate of T282807?

Looks like this is complete, correct?

Great, thank you both!

@Jimman2003 could you validate that this is working for you now on NotWikiLambda?

Is this still an issue? On the frontend at least, I have the user's current languages available to me.

I believe this is resolved?

I was able to replicate this locally with the same tester setup, currently investigating what's going on.

I believe this is done now?

I believe you're correct, yes.

Great, thanks. I was thinking about that second case while working on the new language selector, just created a task and pushed a small patch to allow editing all multilingual strings while in edit mode. This will need to be scoped down more as we add in more user permissions but it'll help in the short term.

The ZObject noted in the description no longer exists on NotWikiLambda, is there a current example that would match this task?

@DVrandecic is this working for you now?

Should this be only for implementations, or all built-in types and persistent objects?

This issue was due to Z802 not having a Z2K4 value, which led to an issue when adding an alias. A patch was just approved to fix this (https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikiLambda/+/715526/3).

This appears to happen to any language when an additional label is added to a language with a label in its own language. I was able to replicate this for Portuguese, German, Tongan, Geez, and English.

Closing, the bug was related to another issue, the content not displaying is valid at this point.

Did some more research on this one. We are using the language code, not the language ZID here, so the above snippet wouldn't cover the issue. I'm also only seeing one usage of this, in the ZObjectSelector (everything else is using the above getUserZlangID). I'm not able to get the list of languages to be anything but 'en' (using userlang).

I think we can remove getZLang altogether, we have another computed property getUserZlangZID that covers this case better I think.

I think so, yes.

I believe this was intended to be in the current phase, correct?

What's left to do on this task?

@DVrandecic can you confirm this is done?

Yep, this is done I think. We'll check it off during today's keep in touch meeting.

It's fine with me, this is done.

This could be related to us landing the patch to use the main namespace instead of a special namespace. CC @Jdforrester-WMF

To the best of my knowledge, yes.

Got it, thank you!

It looks like, from the UI to MW, it's a POST request, but from MW to the orchestrator it's a GET request.

As we have made this change to Z20/Tester, does that mean this task should be closed?

How do we want to determine when this task is completed?

Is Map enabled and available in the system right now?

Example ZObject:

Better question, what's the Z50 that would go with a test failure?

What is the structure for this Z5?

Checking again. @gengh @Jdforrester-WMF @DVrandecic do we have a current example of this? Want to make sure it's still valid.

Since Z2 labels cannot be repeated, do we really want to provide default names for implementations or testers? For implementations, it could cause an immediate collision (using just the function's name) or a near-immediate collision (<name> implementation). Same could be true for testers (as well as the non-Z6/Z40 examples).

Can you clarify where this button should be, or where this label should be updated?

Could you provide a location this is happening? Want to make sure we get all the instances of where this is happening.

This would behave the same as the evaluate function call, with the root function already defined (rather than empty) and not clearable. Is that correct?

So basically the functionality of the evaluate function call page, but specifically for the open implementation?