How do I remove GraphQL mutations related to plugins?

James_Wood · September 9, 2022, 10:07am

System Information

Strapi Version: 4.3.4
Operating System: MacOs
Database: MySQL 8
Node Version: 14.19.1
NPM Version: 6.14.16
Yarn Version: 1.22.19

I opened an issue on Strapi’s Github about a week ago but haven’t had a response there yet. I won’t repeat everything again here, as I’ve outlined it in detail in the Github issue. But, in summary, I’m using the GraphQL plugin and I can’t remove the generated mutations for some of the Strapi plugins from the schema.

All the details can be found here: Cannot remove GraphQL mutations related to plugins · Issue #14287 · strapi/strapi · GitHub

I’d really appreciate it if anyone can help me out with how to do this!

Thanks

SFrinlan · May 26, 2024, 2:23am

2 years later this still isn’t especially clear to me. I’ve tried similar to what you’ve tried in the current version with no luck. I think the problem is that they already disable ShadowCRUD in the plugin:

github.com

strapi/strapi/blob/8d33a8c285192abcf44a37c79c2e1545437c69e3/packages/plugins/users-permissions/server/graphql/index.js

'use strict';

const getTypes = require('./types');
const getQueries = require('./queries');
const getMutations = require('./mutations');
const getResolversConfig = require('./resolvers-configs');

module.exports = ({ strapi }) => {
  const { config: graphQLConfig } = strapi.plugin('graphql');
  const extensionService = strapi.plugin('graphql').service('extension');

  const isShadowCRUDEnabled = graphQLConfig('shadowCRUD', true);

  if (!isShadowCRUDEnabled) {
    return;
  }

  // Disable Permissions queries & mutations but allow the
  // type to be used/selected in filters or nested resolvers
  extensionService

This file has been truncated. show original

and then they manually add resolvers for the mutations and the me OUTSIDE of ShadowCRUD:

github.com

strapi/strapi/blob/8d33a8c285192abcf44a37c79c2e1545437c69e3/packages/plugins/users-permissions/server/graphql/mutations/index.js

'use strict';

const userUID = 'plugin::users-permissions.user';
const roleUID = 'plugin::users-permissions.role';

module.exports = (context) => {
  const { nexus, strapi } = context;

  const { naming } = strapi.plugin('graphql').service('utils');

  const user = strapi.getModel(userUID);
  const role = strapi.getModel(roleUID);

  const mutations = {
    // CRUD (user & role)
    [naming.getCreateMutationTypeName(role)]: require('./crud/role/create-role'),
    [naming.getUpdateMutationTypeName(role)]: require('./crud/role/update-role'),
    [naming.getDeleteMutationTypeName(role)]: require('./crud/role/delete-role'),
    [naming.getCreateMutationTypeName(user)]: require('./crud/user/create-user'),
    [naming.getUpdateMutationTypeName(user)]: require('./crud/user/update-user'),

This file has been truncated. show original

The only thing I can see to do is to override the mutations with custom resolvers and throw an error. It doesn’t remove the mutations from the data schema, though, so it’s not really an answer to your original question.

James_Wood · May 28, 2024, 2:02pm

I’ve added the solution I came up with to the Github issue linked in the original post above. Hope it’s helpful.