Can you elaborate on why this issue was locked?

[bkuhl]

I noticed that #1003 was locked, limiting those who can contribute to it. Can you perhaps elaborate why this was locked rather than just left in a "Closed" state? The community can't collaborate on it anymore.

[bkuhl]

I just spent about an hour trying to get rid of "Edit" and "Edit Attached" options on a relationship, which turned out to be solved by the change in this issue, so it seems to be ongoing from my perspective.

[davidhemphill]

Looked into this. I have a Project resource that belongs to many Tag. I was able to hide the edit attached button by adding a attachTag method to my ProjectPolicy and returning false inside it.

Can you confirm this doesn't work for you?

[bkuhl]

Bah... could've sworn I tried this!! Yeah, that worked for me too. Sorry!

[bkuhl]

I'm understanding more of what's happening here within the policies (putting this here for my own reference).

If you want to disable the "Edit Attached" in the below screenshot so you have to perform the delete/attach separately is when the below contains() check is required.

    public function attachRole(User $currentUser, User $user, $role)
    {
        // Allow items not yet attached to be attachable
        if (!$user->roles->contains('id', $role->id)) {
            return true;
        }

        // Disables "Edit Attached"
        return false;
    }

When attaching, if the contains() step is not present, the Roles dropdown will not contain any records as it's set to false, so the contains() check ensures that on this dropdown Roles that aren't already added to the User will be listed.

To keep things simple, you could just allow the relations to be edited, depending on the desired outcome.