Hi, and yes. It is by design. This is part of the relationship navigation feature. The controllerA is referencing controllerB or controllerC if the entity for controllerA (call it entityA) is referencing entityB as parent or entityC as child. What that affords us is that we can set the "selected" attribute and then show the View dialog for such entity, or we can navigate to the child records for the selected record. I am in the process of creating a series of videos on my YouTube channel that goes over the various features of the CRUD generator, and that will include a discussion on Relationship Navigation. Hope I answered your question.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "Troubleshooting" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Great work, thank-you. I was able to get things working in 0.34.2 fairly easily via netbeans.
Unfortunately I'm seeing lots of cyclic references in controllers. Where ControllerA uses ControllerB and ControllerB uses ControllerA.
Have you seen this much?
Hi, and yes. It is by design. This is part of the relationship navigation feature. The controllerA is referencing controllerB or controllerC if the entity for controllerA (call it entityA) is referencing entityB as parent or entityC as child. What that affords us is that we can set the "selected" attribute and then show the View dialog for such entity, or we can navigate to the child records for the selected record. I am in the process of creating a series of videos on my YouTube channel that goes over the various features of the CRUD generator, and that will include a discussion on Relationship Navigation. Hope I answered your question.