WIP proposal to split into many adapters#76
Conversation
|
Good stuff, I like it ! 🚀 @stafyniaksacha has been migrating a whole bunch of Strapi things to Typescript, when that becomes more available the adapter packages could benefit from a typescript interface as well. |
|
I like the idea too :) Just a small niptipping, can we rename "strapi-middleware-cache-mem-adapter" to something like "strapi-middleware-cache-in-memory-adapter" to avoid confusing with "memcached" ? |
|
I have some suggestions since we have lightly discussed making this a plugin for v4 (in which case the package would be renamed to Likewise since we (Strapi) use the Other than that I totally think this is a fantastic idea. A fellow community member @MattieBelt is working on a search plugin that is planning to use this same structure. (I might suggest hold off on merging this until we figure out how best to rewrite this for v4 though) |
👍 Totally agree
May we start creating an RFC for this plugin ? (I plan to work again on this in one or two weeks) |
For sure, please feel free. I should be free to discuss later this week after the v4 stable release. |
|
Hello @agutoli ! I have implemented the provider system for the V4 release here: https://github.com/patrixr/strapi-middleware-cache/tree/feature/strapi-v4/packages Please feel free to give your feedback! |
This is a proposal to split this plugin into optional cache adapters.
Why?
WIP
This is a proposal only, not fully implemented.