[00:09:11] Personally, I'd really love a syntax that can be copy pasted between wikis (re @amire80: Magic words like {{#invoke are translated by editing the ExtensionName.magic.php file. It's not very accessible to casual editor...) [00:12:38] Oh yes, that's the number one most useful thing, and when I say number one, I mean it. [00:40:53] @vrandecic glad to see int! Can you check this - I'm not sure the javascript converters are quite working yet: Z17104 [00:50:10] Newsletter #160: New Type - Integer [00:50:10] https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2024-06-20 [01:01:30] Yes, Functions using the Integer type can now be created. If you encounter issues, let us know! [01:05:13] That seems to work for me? (re @Toby: @vrandecic glad to see int! Can you check this - I'm not sure the javascript converters are quite working yet: Z17104) [01:13:25] Agreed, it's working now. Perhaps a cache issue. (re @vrandecic: That seems to work for me?) [01:13:56] yeah, could be. I have that sometimes with new Functions, but I haven't discovered much of a pattern yet. Thanks for working on it! [01:22:17] It may be transient, but it's happening again now at Z17127 : https://tools-static.wmflabs.org/bridgebot/b15cec96/file_61892.jpg [02:32:28] Hm, that one stayed in the cache for a bit. Once I made an edit, it got unstuck [02:35:23] (re @vrandecic: Newsletter #160: New Type - Integer [02:35:24] https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2024-06-20) [06:19:01] I think there's a glitch for the 0 test here: Z17213 [06:25:24] https://tools-static.wmflabs.org/bridgebot/11b0eb01/file_61893.jpg [06:45:14] Where do the names in the dropdown come from? I was trying to reproduce one of the tests, but I can't figure out which one is Ajana (Z16938). : https://tools-static.wmflabs.org/bridgebot/2b41e998/file_61894.jpg [06:46:45] I even tried qqx, but it looks like the dropdown is hardcoded? https://www.wikifunctions.org/wiki/Z16972?uselang=qqx : https://tools-static.wmflabs.org/bridgebot/cb394b87/file_61895.jpg [07:24:06] Looks like the list is incomplete and text entry is not possible 🤔 You can work around it by making it a function call and using Z801. (The same applies to Z16098.) (re @Toby: I even tried qqx, but it looks like the dropdown is hardcoded? https://www.wikifunctions.org/wiki/Z16972?uselang=qqx) [07:29:58] All tests are passing 🤷‍♂️ (re @Toby: I think there's a glitch for the 0 test here: Z17213) [07:31:36] I counted 13, I just couldn't show all in the picture. But the one I wanted wasn't listed with the same name. (re @Al: Looks like the list is incomplete and text entry is not possible 🤔 You can work around it by making it a function call and using...) [07:40:06] I only get ten 🤷‍♂️ with no possibility to search (re @Toby: I counted 13, I just couldn't show all in the picture. But the one I wanted wasn't listed with the same name.) [07:42:17] Oops, I'm clearly bad at counting! I also see 10. The one I wanted must have been one of the missing 3. (re @Al: I only get ten 🤷‍♂️ with no possibility to search) [12:19:26] we recently opted for diplaying enums with a selector instead of a open-ended search. the rationale behind it is to proactively bring all valid objects to you, instead of asking people to enter (and know before hand) the specific object name. these items are coming from all objects of type Z16927, see also [12:19:26] https://www.wikifunctions.org/wiki/Special:ListObjectsByType/Z16927. how d [12:19:27] o you all feel about this approach? (re @Toby: Where do the names in the dropdown come from? I was trying to reproduce one of the tests, but I can't figure out which one is Aj...) [12:19:50] this feels like a bug, filing! (re @Toby: I even tried qqx, but it looks like the dropdown is hardcoded? https://www.wikifunctions.org/wiki/Z16972?uselang=qqx) [12:45:33] Once the selector has all the right options in the right language, I think this is a good choice for enums with fairly limited sets. If we enumerate long lists like the elements of the periodic table, then it might be better to make them searchable. (re @internetam1n: we recently opted for diplaying enums with a selector instead of a open-ended search. the rationale [12:45:33] behind it is [12:45:33] to proactively ...) [12:46:31] Thanks. I'll subscribe. (re @internetam1n: this feels like a bug, filing!) [13:00:57] T368147 (re @Toby: Thanks. I'll subscribe.) [13:05:57] totally agree! we initially evaluated whether to use a select (https://doc.wikimedia.org/codex/latest/components/demos/select.html) or a combobox (https://doc.wikimedia.org/codex/latest/components/demos/combobox.html). we then opted for the simpler UI with the select, but we decided to revisit this decision if we observed enums lists to be particularly long. [13:05:57] there also might (?) [13:05:58] be a way to dynamically load a specific component based on the enums lenght, eg. <=10 show as a select, >10 show as a combobox. (re @Toby: Once the selector has all the right options in the right language, I think this is a good choice for enums with fairly limited s...) [13:07:19] 10 may be the wrong cutoff given that our flagships have 12 and 13 items. (re @internetam1n: totally agree! we initially evaluated whether to use a select (https://doc.wikimedia.org/codex/latest/components/demos/select.ht...)