Relationship changes should be reflected in both directions in the store

[mrichar1]

Relationship changes should be reflected in both directions in the store

[mrichar1]

Some observations on this...

It is not generally possible to update both ends of a relationship, since the relationship name is likely to be different at each end, and there is no easy way to determine this. For example people/1 might have a relationship articles pointing to blogpost/10, but the reverse is a relationship called authors.

Additionally, relationships aren't unique - blogpost/10 could have multiple relationships to people/1 - author, illustrator, editor etc.

While there may be some cases where changes can be tracked - like spotting the modification of a single, extant relationship - the general case can't be solved.

What can be done is that the related object can be marked as 'stale', with some kind of reference explaining what relationship change made it so. This would be dropped on a fresh GET of the item from the store.

Marking a related object stale is a modification of store data, so probably would have to happen in the mutation methods called for the 'original' object.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.