Matt Krick

fixed in #8116

This would be amazing! I love graphql-shield, but do not use graphql-middleware. Resolver composition is nice but I do not like it's dot notation for naming. Your nested objects API...

looks good! i didn't realize the stock `composeResolvers` handlers a ruleTree using nested object notation instead of dot notation. It'll be great to have 1 less dependency!

Apollo sticks it on the` astNode` directly, whereas the pattern in @nodkz's example puts it on the `field`. The difference in implementation is pretty trivial, but enough to break it....

just 1 little thing & a merge conflict. merge when ready!

absolutely! the trick is what to do with the jobs coming from the app. if we treated this as a migration, you could run the migration & then update the...

Also see #4125 as an alternative approach.

Additional AC - [ ] turn off anti-spam mechanisms when on a PPMI & not using our cloud saas email. This came up with KR

IS_ENTERPRISE now exists

Constraints: - We need to include the metadata or a reference to metadata in the [SSO Relay State](https://github.com/ParabolInc/parabol/blob/3fd27a15aee921512f26360ba2196e8098bbd67c/packages/server/graphql/queries/SAMLIdP.ts). This allows us to attempt to use the new metadata when logging...