A Call for Stability and Backward Compatibility

[lolafkok]

@Paul_Brats

In regards to entityService, new API response, and Lifecycles:

Technically, the entityService is still there (it doesn’t work exactly like it used to, but it is very close). We did add some backward compatibility options (the v4 header for REST and the GraphQL v4 format option).

Technically the entityService is not still there because localized entries are not working anymore with the removal of the localization-Array?!
Technically you mark something as deprecated but change the behaviour and make it unusable: that’s not deprecated.

@Paul_Brats

Lifecycles still exist, but docSrv middlewares are new. But you bring up many good points, and we need to be more transparent about why we are making specific internal changes.

We need to provide more context. Here are some questions that have come up:

• Why did we need the documents system?
• Why did we need to change the response format?
• Why did lifecycles become less valuable?
• Why is there no localization field anymore?
• Why did we remove the helper plugin?
• Why was there so many changes to the design system?
• Why can’t they modify the admin panel anymore?

Yes.

I would assume that Strapi as product in its current stage (quite long beta, v4 as “we fixed some shit that we’ve messed up”-version) will only get new features, changes regarding security, performance, … .
And not: “Hey, let’s think about how we can change existing core functionalities - the community surely will appreciate that!”.

@Paul_Brats Is there a specific date/month currently planned for the release of v5?