Nested field shows wrong @id

With latest version of everything.

On https://api.test1.startinblox.com/users/jbpasquier/

The field chatProfile shows https://api.test1.startinblox.com/chat-profile/1/

On the admin urlid field of this resource shows it as https://api.test1.startinblox.com/chatprofiles/1/ (404)

And furthermore, the expected one is: https://api.test1.startinblox.com/chatprofiles/jbpasquier/

added BUG label

mentioned in merge request !137 (merged)

Opened an MR which fixes this case: djangoldp-account!63 (merged)

The cause was that DjangoLDP-Account defines redundant urls for accounts/ and chat-profiles/. I don't know if it's intentional because it's implicit, but they use pk as the lookup_field (https://git.startinblox.com/djangoldp-packages/djangoldp-account/blob/e55cdd37e6ca26bbe9015f386f2d3a2d54478033/djangoldp_account/djangoldp_urls.py#L35). As they miss model_prefix in the kwargs, they conflict name with the auto-generated urls (which causes error behaviour in the auto_urlid listener)

I didn't think that it should default to using the pk as lookup_field unless no lookup_field is included in the model meta, so I opened an MR which changes this behaviour in DjangoLDP, too (!137 (merged) )

What's the purpose of those URLs? Shouldn't they be safely removed?

the URLs mean that you can access accounts/chat-profiles using the pk, not just the slug.. I don't know if they're used, they're over a year old, I just thought it was safer to fix them

Pretty sure that we don't need them. A long time ago, in a djangoldp far far away we didn't had the auto-registering route, maybe a leftover.

closed via merge request !137 (merged)

mentioned in commit 96c7549a