Rakesh Emmadi a0b998ad7c subscriptions: respect allow_subscriptions in select permissions (#1235) ... <!-- The PR description should answer 2 important questions: --> ### What <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> <!-- Does this PR introduce new validation that might break old builds? --> <!-- Consider: do we need to put new checks behind a flag? --> Until now the `allow_subscriptions` in select permission is no-op. This PR implements its intended functionality, i.e, do not generate subscription root field schema for models that don't have `allow_subscriptions: true`. ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> - Plumb the `allow_subscriptions` value to namespace annotation. - Modify subscription root field annotations; filter roles by allow_subscriptions. - Add a check in IR generation for the permission and raise an internal error, if the check fails. V3_GIT_ORIGIN_REV_ID: 98120809b1294716c96c190e1b6ec875635b5da1		2024-10-17 16:18:09 +00:00
..
auth	graphql-ws: Tests for WebSocket server (#1191)	2024-10-03 04:42:44 +00:00
docker_schema.json	Fix docker-compose.yaml (#1197)	2024-10-02 11:07:29 +00:00
sample-schema.json	subscriptions: respect allow_subscriptions in select permissions (#1235)	2024-10-17 16:18:09 +00:00