Create new request lifecycles in addition to the current query lifecycles

[derrickmehaffy]

• I have created my request on the Product Board before I submitted this issue
• I have looked at all the other requests on the Product Board before I submitted this issue

Please describe your feature request:

Based on https://github.com/strapi/strapi/discussions/6871#discussioncomment-90811

Creating a feature request for this, we should be passing the ctx into the model lifecycles for various reasons. Off the top of my head I could see some usage in say beforeX to compare new data to old data (maybe some kind of version history or audit log or something).

Yes this could be done via a custom controller but it's far easier to build a model lifecycle in most users cases.

---

Edited based on #8193 (comment)

A rough breakdown per my convo with @alexandrebodin will be something like this (a small part of the new request layer we are planning)

[lauriejim]

This issue has been mentioned on Strapi Community. There might be relevant details there:

https://forum.strapi.io/t/auto-fill-created-by-field/293/4

[alexandrebodin]

As discussed already in the core team. Passing the koa context into the database lifecycles will not happen as it is not the role of the database ot handle http request data.

We need to add a new set of lifecycles at the request level (e.g Rest or GraphQL) that will receive the good context according to the context.

[derrickmehaffy]

I've added a sample from some of our internal planning docs, just note that image isn't set in stone as we are still planning the new request layer. (This sits above the query layer which is more DB focused)

[derrickmehaffy]

This will also apply to throwing errors with custom messages into the Admin, as the current DB lifecycles do not handle this well.

[jordankittle]

I too would like to set the author based on the current user using lifecycle hooks.

[derrickmehaffy]

Currently possible in the v4, marking as closed

You should use route middlewares

[Frankiamme]

@derrickmehaffy , could you give an example of this. I've tried implementing a workaround on v4 from the route middlewares but the ctx.state.user object isn't being passed down to the beforeCreate lifecycle

[derrickmehaffy]

@derrickmehaffy , could you give an example of this. I've tried implementing a workaround on v4 from the route middlewares but the ctx.state.user object isn't being passed down to the beforeCreate lifecycle

Not sure what your asking, how to do what?