yourhead
commented
5 years ago i've moved this to the new bug list and requested your input. as you've described this here i don't think this is really feasible for performance reasons.
but it's not 100% clear what you would build with this sort of thing. i'd like to request that you provide some detail about what you want to build -- the actual use case -- and maybe i can come up with some other way to satisfy that requirement that's not so performance hungry.
Right now Parent and Child stacks are both treated as individual stacks when exporting. Their HTML, CSS, JS, etc are processed individually and exported to the respective locations.
It could be nice if a child stack could be made to be an extension of its parent. When a child stack setting is changed, the parent and all of its child stacks would get processed.
I am envisioning this for larger stacks like Site Styles. I thought that this concept would be great for allowing users to pick what settings/feature they may want by simply adding a child stack into Site Styles. What really makes this tough to do now is with Sass templates. it would be awesome to combine the Sass from child stacks into the processing of its parent stack.
If we were able to have a %slice% concept inside the Sass/CSS we could determine where in the parent code, its children's code would be inserted. I am sure that this could be interesting for other template types as well.
Hopefully I am describing this properly...