Misleading CobiGen instructions for Visitor component about jump-the-queue HOT 5 CLOSED

Hello JKrefting,
The guide is specifying in the titles two things when creating the components:

1. Entity without relations
2. Entity with relations
   This is so done so people can notice that when using cobigen the options are different for entities that have relations or do not.

I will change the text to clarify it further as soon as possible.
Thanks for the feedback

from jump-the-queue.

Now I see the connection, thank you. I think what wasn't clear to me is that the CTO addition facilitates the relations. Maybe it would be clearer if this relation would be highlighted.

from jump-the-queue.

Hello JKrefting,
The issue has been solved by adding the specific step the guide wants the people to repeat. The relation is explained later, when the difference between the cto and eto is explained. Please, review the issue.

Regards, Ctrives

from jump-the-queue.

Hi Ctrives,
where can I see the changed version, https://github.com/devonfw/devonfw-tutorial-sources/wiki/devon4j-components appears to be unchanged.

from jump-the-queue.

Hello @JKrefting,
It seems that github had a hiccup and it didnt update with my first update. The explanation on the step has been changed to the next one clarifying which step you gotta repeat:

Finally we are going to repeat the same process that was used with the Queue component but this time, using Cobigen with our other Visitor component. Once cobigen has finished we can fix one of the compilation error in AccessCodeCto and UcFindAccessCodeImpl related to VisitorEto by manual importing like we learned in the last step.

i am gonna close this issue since it has been solved,

Thanks for the feedback and regards,
trivesc

from jump-the-queue.