Subscription & nested fields

With a subscription:

https://jabber.happy-dev.fr/conference.test1.startinblox.com/happydev_muc_admin
https://api.test1.startinblox.com/circles/

When I post a new member to https://api.test1.startinblox.com/circles/1/members/, I have no notification sent to https://jabber.happy-dev.fr/conference.test1.startinblox.com/happydev_muc_admin.

mentioned in issue management/core-team#3

DjangoLDP-Notifications sends notifications to subscribers on the container_id and resource_id of the saved instance: https://git.startinblox.com/djangoldp-packages/djangoldp-notification/blob/master/djangoldp_notification/models.py#L72

In this case the container is /circle-members/.. A simple solution to this would be to add a subscription for the circle-members container?

I could also look into possible solutions searching the relations on the instance

Could we add an auto-creation of subscription on nested containers on subscription creation?

I looked into this and it's not simple because the Subscription stores only the url of the object/container: https://git.startinblox.com/djangoldp-packages/djangoldp-notification/blob/master/djangoldp_notification/models.py#L55

I might be able to get the model from the view, which I should be able get with the url.. what do you think?

As we can only subscribe on local containers, we don't need to subscribe on object directly, I think you can check the related model from the route pretty easily with a reverse

I've implemented a solution here: 9977d188

Is it hacky to use is_backlink like this? to ensure it only works with depth-1 nested fields (and avoiding an infinite loop)

I don't understand this part:

nested_url = str(self.object) + '1/' + nested_field + '/'

What if we use slugs or 1 does not exists?

This seems really tricky too:

nested_container = Model.resolve(nested_url)[0]
nested_container_url = settings.SITE_URL + Model.container_id(nested_container)

if the circle doesn't exist Model.resolve will still return the value we're using, e.g.

Model.resolve('http://127.0.0.1:8000/circles/1000/members/') 
# (<class 'djangoldp_circle.models.CircleMember'>, None)

This seems really tricky too

I've pushed a commit here which I think improves the readability? a08abd4a

closed

Re-opening, the workaround we pushed does not the trick for Circle/Project members.

The created subscriptions always send the resource itself, but here we need a notification type: update of the whole /circles/X/ resource when /circles/X/members/ changes.

reopened

mentioned in issue applications/hubl#533 (closed)

mentioned in merge request !28 (merged)

closed via merge request !28 (merged)

mentioned in commit 64f778a5