Ares api is finally at a workable state, meaning we can now begin to move from our current SQL based system to API calls via apiv2. Doing this allows us to increase database security and have better control of how data is interacted with.
Proposed Solution
Delete all old SQL code (SQLEngine, models, etc).
Refactor models to fit with new apiv2 data models.
Refactor cogs and core code with new API system.
Possible Alternatives
Instead of using models like before we could opt to use pure API calls, but I feel this would decrease code readability a lot, and also make it much more complicated to perform simple operations like editing a user.
Feature Description
Ares api is finally at a workable state, meaning we can now begin to move from our current SQL based system to API calls via apiv2. Doing this allows us to increase database security and have better control of how data is interacted with.
Proposed Solution
Possible Alternatives
Instead of using models like before we could opt to use pure API calls, but I feel this would decrease code readability a lot, and also make it much more complicated to perform simple operations like editing a user.
Aditional Context
ares-api-v2: https://github.com/reignbit/ares-api-v2