Circular Dependencies

Question

Accepted Answer

@Ginden Sorry, I'm abusing the word "support" here. I'm aware that circular dependencies work, as in, you can compile them, and if you carefully use things in the right order, that it's all 💯(that is, until some future day when you refactor some code and now some other part is using a circular-required module before it's fully loaded, which you have absolutely no way to test for or maybe even kno @Ginden Sorry, I'm abusing the word "support" here. I'm aware that circular dependencies work, as in, you can compile them, and if you carefully use things in the right order, that it's all 💯(that is, until some future day when you refactor some code and now some other part is using a circular-required module before it's fully loaded, which you have absolutely no way to test for or maybe even know about, until it blows up at runtime). This fragile load order is very difficult to maintain in a complex codebase. The best way, also as pointed out by the link you've shared, is to avoid circular dependencies completely. We can use tools like the circular-dependency-plugin or madge to detect them before they happen. But if we do that, then how can we possibly have a many-to-many entity relationship, which is circular by nature, and would be disallowed by our newly adopted toolset? How can one feasibly avoid circular dependencies completely and at the same time use typeorm entity relationships? I know this isn't a typeorm-code problem, but the design of typeorm certainly puts users in a difficult position.

Circular Dependencies

Problem

1 Fix

Solution: Circular Dependencies

@Ginden Sorry, I'm abusing the word "support" here. I'm aware that circular depe

The best way, also as pointed out by the link you've shared, is to avoid circula

How can one feasibly avoid circular dependencies completely and at the same time

I know this isn't a typeorm-code problem, but the design of typeorm certainly pu

Validation

Verification Summary

Environment

Submitted by

Tags