| DVrandecic | |
| Feb 29 2024, 8:45 PM |
| Restricted File | |
| Nov 28 2025, 1:33 PM |
| F70711569: Screenshot 2025-11-28 at 14.26.06.png | |
| Nov 28 2025, 1:26 PM |
| F70711568: Screenshot 2025-11-28 at 14.25.54.png | |
| Nov 28 2025, 1:26 PM |
| F70711567: Screenshot 2025-11-28 at 14.26.12.png | |
| Nov 28 2025, 1:26 PM |
| F70708718: Screenshot 2025-11-28 at 10.54.43.png | |
| Nov 28 2025, 9:55 AM |
| F70708717: Screenshot 2025-11-28 at 10.54.48.png | |
| Nov 28 2025, 9:55 AM |
| F42263179: Screenshot 2024-02-29 at 12.44.24.png | |
| Feb 29 2024, 8:45 PM |
For example, go here:
https://www.wikifunctions.org/view/en/Z10096
On the test
'ora per poi io preparo' is palindrome
the tests fail. Click on the (i) to get the Metadata dialog for the failed test.
It states:
Expected result: { "Z1K1": "Z40", "Z40K1": "Z41" }
Actual result: { "Z1K1": "Z40", "Z40K1": "Z42" }
Instead of the JSON of the ZObjects, we should use the default component to display the object (which would use the renderers)
@gengh Mentioned a while ago that we are not displaying the errors using components on purpose. To make it easier for people to debug. can you confirm that Geno?
No, that's not the case.
We are displaying the object as it comes to make it easier to debug, instead of hardcoding functions that stringify results (e.g. I remember we spoke about this due to a special case that rendered the Z11K2 of a monolingual instead of showing it full)
In this case, we weren't using the default component to avoid bulkiness in this dialog, but we could if we find a way to make it look "good"
I am thinking what edge cases there can be. I would opt for a toggle to switch between rendered and json? I could sketch up something for that
Change #1212533 had a related patch set uploaded (by Daphne Smit; author: Daphne Smit):
[mediawiki/extensions/WikiLambda@master] MetadataDialog: use default component in Metadata dialog for displaying expected/actual values
With long items:
Also I prefer adding it to the code editor for readability and scanability !
 |  | {F70711654} |
| View component | View raw json as text | View raw json in code editor (readonly) |
Without going too much into detail, using toggle component will work in this case. However, there are some quick improvements/Codex adaptation that will make the UI more intuitive and reduce design debt. Here's a proposal:
https://www.figma.com/design/ND0eb8Ub30XxWMCZRSwZCk/T358807-Displaying-expected-actual-values-in-Metadata-dialog?node-id=1-3835&t=Uxno1reMgk6PzsZh-1
Does clicking the links "true" or "false" take the user to another view? Or is it just to highlight the result?
Change #1212533 merged by jenkins-bot:
[mediawiki/extensions/WikiLambda@master] MetadataDialog: use default component in Metadata dialog for displaying expected/actual values
