Cyclic References need to be True Change warnings.
J.Ja
Love this one! This information also makes sense in Add/Remove References Pane to give visibility on the impact of having new dependencies to the factory architecture.
Would really help get some insight from working environment....
tbh it should be an error and not a warning.
warnings can be ignored...
Think warning would be enough. Think with errors, people are gonna fix it with an extra module which still has the cyclic reference only no error anymore.also with errors, think some environments can't upgrade because of the errors (-:
Upgrading with cyclic references will be tough anyways.
The idea is that Service Studio can warn when we try to add a dependency that causes a cyclic reference.
Agree. Currently, the only way to figure this out automatically is Discovery module.
Agree. Many cyclic references happen when you copy/paste something from other espace because also add the references. Show the warning also on service studio will help to identify those situations
We need this, any plans when will it take place?
Hey William,
Although this totally makes sense and is on our radar, we still don't have estimates on when this will be fixed.
Cheers,
Studio should warn you when making circular references, and it should be a VERY blunt warning.
Thanks for your idea!
and how deep should the circular check be?
As deep as possible! :)
Yeah, I don't think Discovery has a limitation?
When adding dependencies from espace1 to espace2 and if espace1 already has dependencies from espace2, throw a warning about possible crossed dependencies.
When creating dependencies, Service Studio should warn the developer, in DEV time.
This will be great if some of the discovery functionality could be embedded into Service Studio to warn you before creating an architectural error.
I agree to this one! Right now, your closest hint of circular reference is when you update dependencies and personally notice the redundancy. This is on the assumption that you update all dependencies in the first place (soft dependencies are prone to this and is still circular).
Sometimes junior developers still don't have any advanced notions of architecture, and this warning would be very useful.