Brainslug

@daawaan4U For the subscriptions we're relying on the already existing events system (used in flows/custom hooks). As these events give partial data we do query the database to get the...

especially the GraphQL Subscriptions part yeah those will all look alike as how it's supposed to work is defined in its spec. Batching the queries when there are a lot...

~Because @azrikahar pointed out an issue with subscribing to `directus_fields` using REST i've disabled subscribing to system collections for this PR in favor of solving this for both GraphQL subscriptions...

> Being able to subscribe to users/files among others will be very important to have 😬 Absolutely agree, the hope was to make it less of a reviewing nightmare by...

> Currently for REST subscriptions, we might not be able to distinguish what collection it is, especially when we're subscribed to multiple collections (unless REST isn't meant to be able...

@azrikahar I was wondering why i could not reproduce this issue 🤦 Turns out i was always setting the `uid` in my tester.  While adding a `uid` effectively solved...

Did you configure the Redis Messenger? @u12206050 https://docs.directus.io/self-hosted/config-options.html#messenger

> Settings -> Role -> Custom Permissions -> Rule -> $CURRENT_USER doesn't work, and an empty array is returned. If replaced with a real user.ID works.  How does this...

This shouldnt work on any branch if the m2m returns more than 1 item unless i missed a fix for this on `main`.

> https://github.com/directus/directus/blob/19b7c77c035416343b0867b75193e89689087071/api/src/utils/get-permissions.ts#L151 > > I believe this is responsible to access $CURRENT_USER, and I couldn't find any references from within the websockets. > Variables seem to be working on rest...