Fruit Picker: Improve story/instructions

[junedev]

Follow up from #1725 (comment)

Some tasks in the fruit picker exercise are currently rather "technical" instead of being phrased in terms of the overall story. Maybe someone has a good idea who to improve this.

https://github.com/exercism/javascript/blob/main/exercises/concept/fruit-picker/.docs/instructions.md

General documentation: https://exercism.org/docs/building/tracks/concept-exercises#h-file-docs-instructions-md

[mannyistyping]

Hi @junedev 👋🏽

I'd be happy to take on this issue if that's alright?

I've been going through the exercises within the Go track and I can see how the instructions on the JS track may come off as "technical"...

ex. " Create a callback to be called when the order is successful`
Write a callback function called onSuccess to be called when the order is successful. It should invoke the imported notify function passing a success message to it.

An alternative could be...

1.Let the user know the order is successful

Define the onSuccess() function that will be called when the order is successful. This function will pass { message: 'SUCCESS' } to the notify() function which indicates that the order completed successfully.

@junedev , Is this more more inline with what you imagine to be less "technical" and more in tune with the story?

Additionally in the Instructions prompt I imagine there could be additional elaboration on the tasks to be completed and some additional backstory to the fruit-picking?
I look at annalyns-infiltration as an example where there is some story and a setting of expectations of what the tasks to complete will be.

[SleeplessByte]

Re-assigned!

[alexmitchelldev]

@SleeplessByte could you take a look at the above PR I submitted please? Also, I noticed #1833 is still open. I'd be happy to look at this as well, please assign to me if you'd like me to 😄.