🚀 feat: create new theme

[tcK1]

Description 📄

This PR creates and exports a new theme, based on new tokens. This new theme can be used on applications by passing the theme prop to the ThemeProvider.

Platforms 📲

• Web
• Mobile

Type of change 🔍

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested? 🧪

Find the places on the doc/labnative that are using the ThemeProvider and add the new theme to it. E.g.:

import { ThemeProvider, v3theme } from '@gympass/yoga';

 <ThemeProvider theme={v3theme}>
  {/* ... */}
 </ThemeProvider>

• Unit Test
• Snapshot Test

Checklist: 🔍

• My code follows the contribution guide of this project Contributing Guide
• Layout matches design prototype: FIGMA
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

[goncalo-matos]

potential issue: isn't this going to require changes in all the components that use the colours directly?

• They'd have to know whether to pick the new and the old. A few components already do it via a variant prop IIRC.
• When we inevitably remove the old one, won't we need to remove the new suffix, creating another potential breaking change?

(there's another discussion here... should the components read the colours directly?)

[tcK1]

We are solving this with the theme: https://github.com/gympass/yoga/pull/723/files#diff-7c44dab781eac6c7c111934646f7760210c5556222abaace43c08a350788f217R7-R18

Components access the values from the theme and not the tokens directly (although they are the same in this case). As you said, using the tokens directly is probably another discussion and I agree we shouldn't be doing this, but having it inside the theme helped us keep everything using the expected colors 😄.

[goncalo-matos]

yeah! I was thinking of just having it done on the theme itself but not exposing it via the tokens. Do you think it's worth it to "hide" these new tokens on packages/yoga/src/Theme/theme/theme.js#theme function?

[tcK1]

Maybe in the future, as it will be a breaking change.

[goncalo-matos]

I meant only the new suffixed ones 😅

[goncalo-matos]

nitpick: I think we shouldn't call it v3 as the yoga package is already on 7 :P might be confusing for who is importing it. What about something like refreshedTheme or newTheme?