Asthma: Spanish Translations

[greinard]

Overview

This branch finishes adding Spanish language support to the Asthma components. All translations were created using ChatGPT. I also added a language toggle to each of the Asthma component stories for easier testing via the Storybook.

The provider report component remains English-only for the time being. We haven't decided yet whether that should support Spanish as well.

Security

REMINDER: All file contents are public.

• I have ensured no secure credentials or sensitive information remain in code, metadata, comments, etc.
  • Please verify that you double checked that .storybook/preview.js does not contain your participant access key details.
  • There are no temporary testing changes committed such as API base URLs, access tokens, print/log statements, etc.
• These changes do not introduce any security risks, or any such risks have been properly mitigated.

Describe briefly what security risks you considered, why they don't apply, or how they've been mitigated.

• No security risks. The primary purpose of this PR is to fill in missing translations for previously existing display strings.

Checklist

Testing

• MyDataHelps iOS app
• MyDataHelps Android app
• MyDataHelps website

Documentation

• I have added relevant Storybook updates to this PR as well.

[ajmenca]

I've only looked a little bit at some of storybook's underlying setup functionality - but the addition of that language toggle feels like something that we could configure to show up automagically somehow? Like some of the stuff you did with the dark mode/light mode toggle - this is a pattern we want to better establish for our Stories - but it would be nice if we could do it without having to copy/paste boilerplate.

[greinard]

Yeah, I agree, it would be nice to have a few of those common control types baked in. I'm not really sure how to do that. I suspect that it will involve the use of some third party storybook plugin(s) to make it happen, but it is something we can explore.

Also, even if we can do that, I'm not sure it will eliminate all the boilerplate, since you'll still need to define the appropriate fields on your args/props interfaces and specify the default values in the args config for each story, but at least we wouldn't need to re-define the argTypes over and over again if we can find a way to reuse those.

[greinard]

Planning to merge this later today if there are no objections or requests for delay. Thanks!

[brandoncharnesky]

Looks good. MDH-ViewBuilder uses a global switch for language, it would be nice if that could be used in MDH-UI as well at some point.

[reneefromhold]

Echoing the desire for this to be at a higher level. lg otherwise

[greinard]

Special thanks to @brandoncharnesky for figuring out a global language picker setup. I have removed the boilerplate code from each of the stories.