Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mistica variables migration #1850

Open
13 of 15 tasks
aweell opened this issue Aug 9, 2024 · 1 comment
Open
13 of 15 tasks

Mistica variables migration #1850

aweell opened this issue Aug 9, 2024 · 1 comment

Comments

@aweell
Copy link
Collaborator

aweell commented Aug 9, 2024

@yceballost
Copy link
Collaborator

yceballost commented Aug 13, 2024

Publishing strategy

Regarding of the strategy to release the new version with the styles2variables migration

I think the best approach is to keep the current libraries instead of creating a duplicate of mobile and desktop libraries.

Pro:

  • Avoid double maintenance
  • Avoid duplication of published libraries, so, the library usage will be easier for designers
  • Keep the same library analytics
  • Custom plugin will relink instances to original styles (current files where Themer was used have deprecated styles)
  • Avoid Figma Swap workaround from old libraries to new one
  • Force teams to update

Cons:

  • Breaking changes for teams that want to migrate to new version
  • Themer wow will be deprecated and teams can't use it (if they update libraries)
  • Custom plugin to help team in the migration, possible unstabilities and bugs.

Teams that not update can continue using Themer but new instances will need variables, so this kind of teams will work with the old and the new wow. (Themer + Variable)

Duplicate current library doesn't fix the problem with styles changed by Themer, so this strategy is not very profitable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

2 participants