-
-
Notifications
You must be signed in to change notification settings - Fork 195
Future Planning
Kevin R. Whitley edited this page Feb 18, 2019
·
4 revisions
To keep this out of issues/PR maintenance clutter, the planning for next gen apicache will occur in the Wiki.
Base Plan/Requirements:
- ES6 - apicache should be developed in an ES6+ environment, but transpile down to as low of a core Node version that we're able. This should include tests to allow running tests in each of the supported Node version environments.
- PR/contrib - there should be a clear PR checklist for contributing to keep contributions clear and productive
- Decouple stores - the store implementation should be astracted and removed from the core code. Stores should have a common interface exposed to allow quick replacement and 3rd party integrations.
import apicache from 'apicache/redis'
import apicache from 'apicache/memory'- users would like to see more info about cache, e.g. when route was cached, etc
- stores should maintain own index to allow rebuilding (e.g. redis)
- stores should be address multi-node concerns (or at least consider)