Hello everyone,
To avoid having spaghetti code, I'm putting one asmdef file in every package. That way if there's a cyclic dependency in packages, the code just doesn't compile. It's a principle I used to follow in my non-game dev days.
I've now ended up with 109 asmdef files and csprojects in Rider.
I'm wondering if any veterans can help figure out if this is the right approach.
1) Is this a bad approach for the unity build system - as in does it slow down the build?
2) Is there a way to...
One asmdef file per package?
To avoid having spaghetti code, I'm putting one asmdef file in every package. That way if there's a cyclic dependency in packages, the code just doesn't compile. It's a principle I used to follow in my non-game dev days.
I've now ended up with 109 asmdef files and csprojects in Rider.
I'm wondering if any veterans can help figure out if this is the right approach.
1) Is this a bad approach for the unity build system - as in does it slow down the build?
2) Is there a way to...
One asmdef file per package?