feat: add block mutations

[capJavert]

AS-651

• add block mutations for all supported entities so far (with backward compatibility)
• squad entities (from other feat: squad content preference #2378)

[rebelchris]

Nothing blocking

[rebelchris]

Not 100% sure, but do we also need to introduce the other side backward compatibility?
So the current block flow to set contentPreference?

(Maybe you did this in other PR already, can't recall)

[capJavert]

I did add it, blockKeyword also saves to Feedtag with blocked: true and blockSource saves to FeedSource.

Do we do anything additional with blocking?

[sshanzel]

Looks good to me. One question though, why does blocking and unblocking looks similar in terms of notificationPreference. They both have 0 entry on that entity, shouldn't we add an entry with blocked = true so that even default notifications won't be sent as they are blocked, if I understand correctly.

[capJavert]

@sshanzel in both cases we wont to remove all notification preferences so user is not subscribed to anything, does that make sense?

They both have 0 entry on that entity, shouldn't we add an entry with blocked = true so that even default notifications won't be sent as they are blocked, if I understand correctly.

We do add blocked: true for FeedTag and FeedSource for backward compatibility.

[sshanzel]

@sshanzel in both cases we wont to remove all notification preferences so user is not subscribed to anything, does that make sense?

They both have 0 entry on that entity, shouldn't we add an entry with blocked = true so that even default notifications won't be sent as they are blocked, if I understand correctly.

We do add blocked: true for FeedTag and FeedSource for backward compatibility.

Thank you for the clarity, yeah, I was just wondering if it should also be the case for User entity. This is so, for example, when you are mentioned by the blocked user, you won't get notified, since your preference is blocked.

[capJavert]

@sshanzel yeah, currently you can't block an user (at least from UI) so it will be a silent feature, but for sure good idea for when we want to introduce it.

[capJavert]

Leaving role in db for now so I can copy data