I have two entry points that share some code. One of my entry points has some code that isn't shared, but results in a circular dependency.
I would expect that the circular dependency in non-common code end up in the entry point specific output file, but instead it is ending up in the common file. If I remove the circular dependency, it ends up in the entry point specific output file (as I would expect).
Consider the following situation
I have two entry points that share some code. One of my entry points has some code that isn't shared, but results in a circular dependency.
I would expect that the circular dependency in non-common code end up in the entry point specific output file, but instead it is ending up in the common file. If I remove the circular dependency, it ends up in the entry point specific output file (as I would expect).