It would nice to catch circular dependencies in the DQMH Validator Tool. Catching all circular dependencies would be hard ie A->B->C->D->A, but the simple case would be easy to catch A->B->A. This would be the case where A registers for the broadcasts of B but also sends requests to B.
If anyone has an easy way to catch the more complicated case, I'd be all for that too.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Taggart,
Thank you for your suggestion. That would be an interesting piece of information to get for the developers.
That being said, we don't think the validator is the right place to implement this feature.
A tool like Antidoc could be a better way to get and display it.
Thank you again for your time sharing your idea to make the DQMH framework better than ever!
Olivier