I calculated that I have 13 and a quarter weeks to go if I manually sift through making 2087 component states. I have attached screenshots attached at the bottom--they are of the Excel spreadsheet with the total amount of labor, some of the 18 artboards, and then the current state of the components compared to the desired state of the components. Now, this process is highly replicable, and as such, should have a solution through code.
My code thus far has been logging in order to determine the appropriate route to take...it is attached here:
This exports the base level of childNode, the name of the childNode within, and a boolean value of whether the childNode is the main/Master component or not. It works great and logs what I need it to.
But, I cannot determine how to add a new "Component State" (as seen below this paragraph) in code. I found this on the documentation for symbolInstance:It is not currently possible for plugins to create a new component definition or a new SymbolInstance node, aside from using commands.duplicate to clone existing SymbolInstances.
Does this mean that I cannot have code copy an existent vector into a code-created new "Component State" for me? Or am I mistaken?