Issue with plugin content types and admin routes

[kevinvugts]

Hi @ComfortablyCoding

There is an issue with this plugin.
Individual plugins contentTypes cannot be transformed individually. The only thing that works is basically allowing them all by proving the "id" of the plugin in the plugins.ids object. However, it would be nice if we could allow individual contentTypes like you can with the contentTypeFilter "api::content-type-name.name"

I checked your code in the register.js and it seems to be because the way you are checking the UIDS from the strapi[apiType].

This config does seem to pass some checks

  "some-plugin": {
    enabled: true,
    resolve: "./src/plugins/some-plugin",
  },
  transformer: {
    enabled: true,
    config: {
      responseTransforms: {
        removeAttributesKey: true,
        removeDataKey: true,
      },
      contentTypeFilter: {
        mode: "allow",
        uids: {
          "some-plugin": true, // This line bypasses the checks in isAvailableApi and isAvailableMethod. However it does not allow for allowing individual content types from a plugin..
          "api::blog.blog": true,
        },
      },
      plugins: {
        mode: "allow",
        ids: {
          "some-plugin": true,
        },
      },
    },
  },
};

However, as you can see I have to remove the plugin:: prefix to make it pass those checks.
Also, admin api routes are not transformed on purpose, this shouldn't be the case since these should also be able to be transformed.

Can you support this?

strapi-plugin-transformer/server/register.js

Line 70 in 3cb7855

// skip admin routes

[kevinvugts]

I opened up a pull request #105

[ComfortablyCoding]

As discussed I am unfortunately no longer maintaining this plugin nor do I have the permissions to merge any longer.

A maintainer would need to take this over and review as needed.

P.S. The PR is present for anyone who wishes to patch it for themselves in the meantime.

[kevinvugts]

As discussed I am unfortunately no longer maintaining this plugin nor do I have the permissions to merge any longer.

A maintainer would need to take this over and review as needed.

P.S. The PR is present for anyone who wishes to patch it for themselves in the meantime.

Thanks for your response. As discussed per Discord I am unable to maintain this library either. Anyhow, for anyone that wants this change. Please do!