-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Schema Load Lifecycle RFC #15
base: master
Are you sure you want to change the base?
Add Schema Load Lifecycle RFC #15
Conversation
Signed-off-by: Diogo Correia <[email protected]>
Hi @diogotcorreia can you add a link to the preview of the RFC in the description plz :) |
Done :) |
Thank you for this RFC @diogotcorreia. I will review it in details. Just to give you more info, we are planning on refactor the DB layer a lot before the end of year and we will certainly support some sort of schema lifecycles to do any customization. If we were to implement something now be aware we will probably break it for Strapi v4 :) |
Thanks for this RFC. Here are somme comments:
|
@alexandrebodin can you expand on this suggestion? |
Signed-off-by: Diogo Correia <[email protected]>
@alexandrebodin |
Thanks for the improvements ! I think the lifecycles arguments should be passed as an object so we can make it evolve without breaking changes and have potentially different infos per connectors. Other stuff I would like to see (to answer @derrickmehaffy) There are a lot of possible events. I need to review our process but here is what comes to my mind:
Once we define the exact events we can define the APIs for each of them |
Addresses issue strapi/strapi#5972
As requested, here goes my RFC about the schema load lifecycle.
Preview Link: https://github.com/diogotcorreia/rfcs/blob/0005-schema-load-lifecycles/rfcs/0005-schema-load-lifecycles.md