Jump to content

User talk:AAlhazwani (WMF)

From Wikifunctions
Latest comment: 9 days ago by AAlhazwani (WMF) in topic Description and input labels of Z21053

Welcome to Wikifunctions, AAlhazwani (WMF)!

Wikifunctions is an open repository of code functions that anyone can use and contribute to!

Do you need some help getting started? Here are some pages you can familiarize yourself with:

  • Introduction – An introduction to the project.
  • Community portal – The portal for community members.
  • Contents – The main help page for editing and using the site.
  • Glossary – Definitions of frequently used terms.
  • FAQ – Frequently asked questions.
  • Project chat – Discussions about the project.

Please remember to sign your messages on talk pages by typing four tildes (~~~~); this will automatically insert your username and the date.

If you have any questions, don't hesitate to ask on Project chat. Once again, welcome, and I hope you quickly feel comfortable here, and become an active contributor to Wikifunctions.

Best regards! VIGNERON (talk) 17:10, 5 November 2023 (UTC)Reply

Description and input labels of Z21053

Hello! What would you recommend be used for the description and labels of the convert function. I know that the description and labels are not good, but I'm not sure how to improve them. Thanks, and Happy holidays! Feeglgeef (talk) 04:22, 22 December 2024 (UTC)Reply

One solution I would not be opposed to is having Z21053 be the convert function intended primarily for use on WF, which would have lowercase names and inputs, and having another convert function for use on WP (composition of Z21053 that would use title case and would be easier to use for users without technical experience. Feeglgeef (talk) 05:39, 23 December 2024 (UTC)Reply
I've created a function for this, Z21098. Feeglgeef (talk) 06:00, 23 December 2024 (UTC)Reply
i'm guessing you've seen the draft that i've been working on :) i don't have a strong opinion about this, actually i think it's up to you and the rest of the wikifunctions community to decide in how far you'd like to take those suggestions into account, and what's the best strategy to do that. i'm currently on leave, but i'm planning to finish the draft and publish it hopefully by the end of january. thank you, and happy holidays! AAlhazwani (WMF) (talk) 16:16, 23 December 2024 (UTC)Reply
hey! thanks for reaching out. while looking at the function input labels i was wondering if there is anything that we could do to be more concise. for instance, instead of starting quantity, could we opt for something like value, number or amount? and for the starting units could something like start/end unit or from/to unit work as well?
specifically to the function description, it would be interesting to consider in how far we need to provide written examples or if could rely on the existing interface to let people learn by doing. i see that right now users have to provide a unit in written form, but we could imagine a future where they would pick a unit from a list (displayed as a dropdown), possibly using enums. so, in that scenario, would a description like Converts a value from one unit of measurement to another work?
let me know how you feel about those ideas :) AAlhazwani (WMF) (talk) 16:11, 23 December 2024 (UTC)Reply
I've implemented your suggestions on Z21098. Thank you for helping out while on leave! Feeglgeef (talk) 17:13, 23 December 2024 (UTC)Reply
Could you also provide input on Z21425? I've tried to create it as a wrapper for Z20756 to make more sense to put on wikis. It currently times out, so I'll try some things to speed it up. Feeglgeef (talk) 23:20, 7 January 2025 (UTC)Reply
question: is the function intended for displaying a date range eg. 1 January 2000 - 31 December 2024 or for returning the age of a date range, eg. 24? i'm asking because based on the desired function scope there might be different opportunities to improve the UX copy and make it more clear. thank you! AAlhazwani (WMF) (talk) 11:59, 8 January 2025 (UTC)Reply
It always displays the age, but there a boolean options on whether to display the dates, so, from Wikipedia:Jimmy Wales, it would display something like 58 or 58 (August 7, 1966 - ), depending on what is selected. Feeglgeef (talk) 13:47, 8 January 2025 (UTC)Reply
understood, thanks for the extra clarification! given this info, i tried out how the existing content might look and feel on the upcoming function UI on wikipedia (in the mock-ups i'm assuming that we're going to have display and reading functions for the date type). i then explored how we might give additional details with the function description. i was also wondering if the Is alive? argument is needed, or if we could rely on the omitted second date to assume that. i hope this is helpful food for thoughts!
Mock-up of the editing funciton UI on Wikipedia exploring different UX copy options
Mock-up of the editing funciton UI on Wikipedia exploring different UX copy options
AAlhazwani (WMF) (talk) 15:54, 8 January 2025 (UTC)Reply
The second date couldn't be omitted because of the enforced determinism. Someone would have to put a {{CURRENTDATE}} in there to make it the current date and the function couldn't check if the input was the current date. Feeglgeef (talk) 16:56, 8 January 2025 (UTC)Reply
I've created phab:T392165 to address this now that we have a working integration. Feeglgeef (talk) 13:29, 18 April 2025 (UTC)Reply
thanks @Feeglgeef! JFYI i recently moved to the growth team. from now onward, feel free to ping @GOnyeahialam (WMF). AAlhazwani (WMF) (talk) 14:01, 18 April 2025 (UTC)Reply