Remove Requirement for Foreign Keys
Currently, it appears that in order for navigation properties to work, they must be coupled with an explicit FK property that contains the value for the relationship. This leads to entity contract pollution and should be eliminated, if possible.
I am having to modify my models to comply with Breeze, and that is a poor development experience.
Thank you for any consideration,