You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, there's some minor formatting inconsistencies in the readme (which I'd be happy to make a PR to fix), and I feel the base class could use more straight forward code with less hidden variables. As far as I understand, Config's purpose could be completely encapsulated within Base, too.
Then the code uses .spread quite a bit, which is bluebird-specific and doesn't exist in es promises. This might break future knex implementations (there is intent to do it: knex/knex#2936, knex/knex#1588). I could possibly prioritize this?
This is great and I love that it exists, blowing complicated ORMs out of the water.
But I've felt reluctant to use it simply because it hasn't been updated in 3 years.
There are a decent amount of tests, and everything still seems relevant to me.
Is there anything else that might need maintenance, to keep the project active and make people like me more confident in picking this tool?
The text was updated successfully, but these errors were encountered: