You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when users import variables we only create or update a token set with the name of the collection.
However, we do not create theme groups for them. This leaves users with half the job done, and half still to do manually. We can optimize this.
Introducing theme group creation on import
When importing variables, we will from now on
look at the name of the variable collection and the modes that would be imported, for this example let's use Collection name: ThemeMode name: Light
inside the plugin, look at if the user is a [Pro] user. If they are NOT, do nothing
if they are a [Pro] user, check to see if they have any theme groups, and if so, if any theme group's name matches the collection name
if no theme group name that we need exists
create a theme group with the name of the Collection
inside that theme group, create theme options with the name of each Mode, with the "enabled sets" as the sets that is used for that (which we even today create or populate, so we have that logic in already, we just need to create the theme options with the right sets)
if a theme group exists already with that collection name
Look at the theme options to see if we need to create any new ones, or if we can leave it as is
The text was updated successfully, but these errors were encountered:
Currently when users import variables we only create or update a token set with the name of the collection.
However, we do not create theme groups for them. This leaves users with half the job done, and half still to do manually. We can optimize this.
Introducing theme group creation on import
When importing variables, we will from now on
Collection name: Theme
Mode name: Light
[Pro]
user. If they are NOT, do nothingMode
, with the "enabled sets" as the sets that is used for that (which we even today create or populate, so we have that logic in already, we just need to create the theme options with the right sets)The text was updated successfully, but these errors were encountered: