Migration of asset links to CC libraries leads to duplications and unnecessarily large libraries
We are using the Atomic Design approach and have built our files accordingly. There is an underlying pattern library with all the atoms. Then there is one file for each molecule, these files use the atoms. Finally, there are the files of the programs that plug atoms and molecules together. This file structure isn't entirely because of Atomic Design, but also because we are running into performance problems with our rather big files otherwise.
With the old feature of linked assets that was never a problem, now we started to using the Library feature and are running into issues:
I started with migrating the components of your Pattern Library (Atom file) into a library. Then I went on with one of the molecules. This one is using the Pattern Library, but also will be used by the program files, therefore it needs to be a Library itself. In my head that's totally fine, because it uses assets of the Pattern Library but has its own local assets that should be in the new molecule Library. But when I uploaded the molecule as a library all the assets of the Pattern Library were "duplicated" so every color, font and component from the Pattern Library is uploaded into the molecules Library as well. This seems like a bug to me, because the molecule file knows that those are assets out of the Pattern Library and also shows them with the link symbol and gives the option to edit them in the source file. But it's not possible to delete them out of the molecule library or at least the Document assets which are uploaded into the library.
With our file system that would mean that all the molecules would be really big libraries that duplicate the Pattern Library + 5-10 local components.
Does anybody have the same issues with the new update that forces you to use the library functionality instead of linked assets? Is there a solution to not run into this problems other than changing our whole file logic?