CAP Documentation: Associations

[#1]

The documentation here in CAP for associations describes unmanaged, managed to one and managed to many associations.

The examples use the entities Employees and Addresses.

Each time I read this section of the document, I find myself having to stop and think carefully. The cause of my "cognitive load" is the knowledge that employees can have many addresses, like a home address, work location address, postal address and in some cases, these addresses are shared amongst employees - like work location address. My brain leaps to a many to many association and I struggle a little with the dissonance between the documentation text and the illustrative example of employees and addresses.

Do others find this also? Is this a potential opportunity to change the example to make it more obvious?

[Daniel7 · Accepted solution]

I agree, Andrew → will fix it for the upcoming release (next week)

Sometimes Food and Bars are less problematic, probably 😉 ... just kidding; we'll find something less misleading

[Daniel7 · Accepted solution]

"Food" was auto-corrected from "Foos" ... but maybe something around food bars would in fact be cool