Federation: Don't serve distant resource Data

Related: djangoldp-account#43 (closed)

Currently, distant resource are also served on local container. It leads to duplicate & glitched content, they should not, they must contain only their @id without anything else.

See: https://api.test2.startinblox.com/users/ & https://api.test1.startinblox.com/users/jbpasquier/

mentioned in issue djangoldp-account#43 (closed)

mentioned in merge request !119 (merged)

MR open for this !119 (merged)

This MR only prevents the glitched content being returned for the federated resource itself. For example if I visit http://localhost:8000/profiles/ I'm still given the profile attached to my federated user

{"@id":"http://localhost:8000/profiles/f31780a3-97f5-4b19-9e93-773da8625116/","slug":"f31780a3-97f5-4b19-9e93-773da8625116","available":null,...}

I think that to prevent this we need to prevent the profile itself from being created.. am I right in thinking that the only fields which should be set for a remote user are the urlid, username, email and name?

We don't really cares as long as we never serve them. But for a clean way, it should be better to don't create them, yes.

MR opened for this as well: djangoldp-account!50 (merged)

@calummackervoy I have some weird behavior on test2. https://api.test2.startinblox.com/users/

Like this one: https://api.test2.startinblox.com/users/c76275a4-8cc5-4ab4-a0ad-a6a3f015e6a6/ who is on the list and have datas (?).

Or this one: https://api.test2.startinblox.com/users/0339d4d8-9a1e-4106-b894-afe70c7f548d/ who is also served on the parent container, with right urlid ( https://api.test1.startinblox.com/users/jbpasquier/ ) but should not, causing it to dup on the menu.

changed the description

changed title from Federation: Don't serve distant resource to Federation: Don't serve distant resource Data

changed the description

I've split this into two separate issues for clarity: #215 (closed)

closed

mentioned in issue management/core-team#3

changed milestone to %0.7