Hi 👋

I have been wrestling all day with the new Strapi version. I used v3 and understood what was happening with the JSON response. The new version seems needlessly complicated 😿. I found your plugin on a forum post. I'm not sure if I am missing a step, but my data is not being transformed (as far as I can tell).

• I installed and added the plugin config as you wrote in the readme. Package.json looks good. Config is in a top-level folder.
• I also restarted both servers.
• My console output remains the same.

In v3 I was able to .map over my response, but with attributes being an object inside of data now, I'm lost.

If it helps to know, I am receiving the data with a fetch request and using getStaticProps to connect the data to the front-end. The map function is aware there are five items in the array, but can't access anything further.

Is there something else I need to change? I'm using Strapi and Next.js. I was ecstatic to find this after a long day. I hope I can get it working. Thank you for your help 🙇‍♀️.

Hello! Thanks for the plugin!

I'm trying to use transformer in a strapi v4 app. When calling the endpoint the data is not transformed. I followed the documentation and it still didn't work

my ./config/plugins.js

module.exports = ({ env }) => ({
 'transformer': {
    enabled: true,
    config: {
      prefix: '/api/',
      responseTransforms: {
        removeAttributesKey: true,
        removeDataKey: true,
      }
    }
  },
});

my package.json

    "@strapi/plugin-graphql": "^4.2.0",
    "@strapi/plugin-i18n": "4.2.0",
    "@strapi/plugin-users-permissions": "4.2.0",
    "@strapi/strapi": "4.2.0",
    "pg": "8.6.0",
    "strapi-plugin-ckeditor5": "^2.1.1-rc.1",
    "strapi-plugin-transformer": "^2.0.2"
  

In strapi version 4.0.7, getting response like below

{
  "data": {
    "id": 1,
    "title": "the title",
    "componentA": {
        "id": 1,
        "content": "Hello!",
    }
    "createdAt": "2022-02-11T01:51:49.902Z",
    "updatedAt": "2022-02-11T01:51:52.797Z",
    "publishedAt": "2022-02-11T01:51:52.794Z",
  },
  "meta": {},
}

But when I upgrade strapi to version 4.1.0, the response I get is like below

{
  "data": {
    "id": 1,
    "title": "the title",
    "componentA": {
        "data": {           <--- here
            "id": 1,
            "content": "Hello!",
        }
    }
    "createdAt": "2022-02-11T01:51:49.902Z",
    "updatedAt": "2022-02-11T01:51:52.797Z",
    "publishedAt": "2022-02-11T01:51:52.794Z",
  },
  "meta": {},
}

Strapi version: 4.1.0 Plugin version: 1.0.3

Not supported in new strapi versions.

"@strapi/strapi": "4.5.2", "engines": { "node": ">=14.19.1 <=18.x.x", "npm": ">=6.0.0" },

Hi

Thanks for an awesome plugin :-)

I just wanted to let you know that I have submitted this issue: https://github.com/strapi-community/strapi-plugin-rest-cache/issues/25

The gist of it is this: "When using strapi-plugin-transformer and rest-cache plugin only the first request from api is transformed. Subsequent and therefore cached api requests are not transformed".

I'm guessing it mostly has to do with rest-cache plugin not taking transformer in to account, but I don't know.

In Strapi v4* (and already using strapi-plugin-transformer) when populating fields, the joined entity comes back flatten as expected :+1:

However, they have also added a data field, so you get something like:

{
  image: {
   data: {
      id: 1,
      //...
    }
 }
}

it would be great if, like with the attributes field, the response is flattened to:

{
  image: {
      id: 1,
      //...
 }
}

not sure how complex this would be but just a thought

Hi,

this plugin was just presented in the Strapi Community Call and it looks potentially very useful to solve a problem that my team currently faces:

We're currently migrating from v3 to v4. I understand that v4's API responses are structured significantly different from v3's API responses and it looks like your transformer plugin brings v4's API responses closer to the format that v3 returned. This could potentially simplify the refactoring that is needed in our applications that consume data from Strapi or at least allow us to do it step by step.

Would it be possible to enable or disable the response transformation executed by your plugin by route (e.g. with a more atomic configuration) or by request (e.g. by providing a certain request header)?

Hi,

I have installed the plugin in my Strapi v4.1.12 and update the plugin.js as mentioned in the docs but the response is not transforming. I have also tried restarting the Strapi.

My dependencies are as follows:

...
 "dependencies": {
    "@strapi/plugin-i18n": "4.1.12",
    "@strapi/plugin-sentry": "^4.1.12",
    "@strapi/plugin-users-permissions": "4.1.12",
    "@strapi/strapi": "4.1.12",
    "pg": "^8.7.3",
    "strapi-plugin-import-export-entries": "^1.2.0",
    "strapi-plugin-transformer": "^2.0.1"
  }
...

plugin.js

module.exports = ({ env }) => ({
  sentry: {
    enabled: true,
    config: {
      dsn: env('SENTRY_DSN'),
      sendMetadata: true,
    },
  },
  'transformer': {
    enabled: true,
    config: {
      prefix: '/api/',
      responseTransforms: {
        removeAttributesKey: true,
        removeDataKey: true,
      }
    }
  },
  'import-export-entries': {
    enabled: true,
  },
});

Tested with and without the plugin, deep relations don't seems to work with the plugin turned on.

like if i retrieve posts content-type with user relation, it would work

But if i try to retrieve user's relation like user.profilePic, it won't work

Since this plugin mainly used to reduce unnessary nested object for api. Need same feature for graphql.

Since graphql return body as string, that transform logic doesn't allowed to transform.

Below code change is to add logic for grapghql.

if (isAPIRequest(ctx)) {
	const { data } = ctx.body;

	// ensure no error returned.
	if (data) {
		ctx.body['data'] = getPluginService('transformService').response(settings, data);
	}
}

to

if (isAPIRequest(ctx)) {
	if(_.isString(ctx.body)){
		ctx.body = JSON.parse(ctx.body);
	}
	const { data } = ctx.body;

	// ensure no error returned.
	if (data) {
		ctx.body['data'] = getPluginService('transformService').response(settings, data);
	}
}

Not supported in new strapi versions. Supported in Node Versions- "engines": { "node": ">=14.19.1 <=16.x.x", "npm": ">=6.0.0" },

Not Supported in Latest Versions- "engines": { "node": ">=14.19.1 <=18.x.x", "npm": ">=6.0.0" },

Background

When we send a POST or PUT request to a content API, Strapi asks us to wrap the object in a data key, which is also tedious like data keys in responses.

GOOD:

{
	"data": {
		"name": "foo bar"
	}
}

BAD:

{
	"name": "foo bar"
}

The "BAD" example will get an error response, like this:

{
    "error": {
        "status": 400,
        "name": "ValidationError",
        "message": "Missing \"data\" payload in the request body"
    }
}

Behavior

Auto wraps the body of requests within a data key, transforming the "BAD" example above to the "GOOD" one.

I suppose we can do this in the middleware, too.

Config

I propose a new config key:

| Property | Description | Type | Default | Required | | -------- | ----------- | ---- | ------- | -------- | | requestTransforms | The transformations to enable for the API request | Object | undefined | No | | requestTransforms.wrapWithDataKey | Wraps the request body with data key if needed | Boolean | false | No |

Love this plugin. Thank you for your excellent work!

I can compose a PR if you like this proposal. :wink: