Replies: 2 comments 1 reply
-
I don't think this would be performant since there are too many things that need to be done. First, we need to get the package name from the It's much easier to manually add DependsOn and you have more control over it. |
Beta Was this translation helpful? Give feedback.
-
Hi @EngincanV , thanks for your reply. From my understanding, "many things" you mentioned has already been done in Plugin system.
"Auto Depend On" doesn't need first 2 steps since it still needs to reference packages manually, step 3 and 4 are same as Plugin. The key thing is that regardless of the implementation efforts, is "Auto Depend On" reasonable ? |
Beta Was this translation helpful? Give feedback.
-
Current ABP's module system needs explicitly adding
DependsOn
attributes on a module class to declare its module dependencies.IMO if a module A referenced another module B, A must depend on B right?
So is
DependsOn
necessary actually?Let's think it in the opposite way, is there a case that module A has referenced module B, but A does not
DependsOn
B?If there is no such case, is it possible to implement something like "Auto Depends On"?
That is, once you reference another ABP module in your module, you automatically create an implicitly dependency relationship with it.
Beta Was this translation helpful? Give feedback.
All reactions