feat: wrap request body with data key

[cssmagic]

Just a rough POC for #51 .

There are still some problems to resolve.

[cssmagic]

I just added a draft PR, remaining two problems to resolve/discuss:

Avoiding polluting non-Content API requests

In a middleware, ctx is incomplete before Strapi handles the request, so it's not easy to recognize Content APIs.

I don't have a perfect solution for this. But two ugly workarounds: 😔

• Prepare a list of Strapi's built-in APIs, such as auth APIs and ones provided by other plugins. (Sounds bad)
• Ask users to announce path names of their Content APIs, via a new config key. (Sounds better)

Possibility of "Smart" mode

In the beginning, I believed we could wrap with data key smartly -- if it has no data, we wrap; if it has, we ignore.

// in middleware
let reqBody = ctx.request.body;
if (!('data' in reqBody)) {  // 👈 "smart" detection
	reqBody = { data: reqBody };
	ctx.request.body = reqBody;
}

Unfortunately, this "smart" detection could be wrong, if an entry object has its own data field:

// body of a POST or PUT request
-{
	"foo": "...",
	"bar": "...",
	"data": { /* ... */ },
}

The above needs to be wrapped, but the "smart" detection failed to figure out.

Then I realized there's no way "smart" enough.

Might as well set this feature as "Force" mode -- if the config is on, we wrap; if not, we do nothing.

[ComfortablyCoding]

Great start! I have refactored some of the code (using your work as a base) to be more inline with the rest of the codebase.

Avoiding polluting non-Content API requests

I am not a fan of either of those options, I will need to think more on this. I was originally thinking we can check if the API prefix is present but that will lead to the same issue that the responseTransforms had in #25

Possibility of "Smart" mode

Good catch. I am okay with doing this in "force" mode. If anyone reports an issue we can revisit this functionality.

[cssmagic]

Thanks 😉