Hi,
It's been a while since I posted an idea. But this one is something that would be very useful to the team I'm currently. I work at a studio where characters get loaded in from different referenced files, so exchanable items (i.e cloth) can be loaded separately. And all the connections the need be made between the files get stored as code separately. We are currently having the problem, that a few very specific attributes are getting cycle checkend when those connections from code are being made, but don't cause cycle checks when being fully connected. With the current cycle check warning there is virtually no possibility to exactly know where it comes from, how to fix it or if it will cause problems down the line. It would be cool if instead of "-e off", cycle check also had the option "-e whole" or something along those lines, to show the whole cycle for people with more experience. So problems like the one we are experiencing, where a cyclecheck warning gets thrown during a script, can be better analysed.
I think this shouldn't be too hard to implement, since cyclecheck has to run some kind of analysis where it finds the whole cylcle anyway, right?
Boring as it may be. This is my current Idea, and it would help me, my team and probably a lot of other tech savy people a lot.
Thank you for considering.
