Before coding a patch, I prefer to show you my case and tell me if I forget to configure something or if there is a workaround.
The problem is when a collection is fetched with options and that collection model has a 1:M relation, those options are propagate. The side effect is an error when backbone-associations define the relation.
Hi,
Before coding a patch, I prefer to show you my case and tell me if I forget to configure something or if there is a workaround.
The problem is when a collection is fetched with options and that collection model has a 1:M relation, those options are propagate. The side effect is an error when backbone-associations define the relation.
So should I explore further and create a patch?