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
Sadly, Dancer::Plugin::SimpleCRUD is currently D1-only.
I very much want to make it work with Dancer2, but just haven't had the time to spend on it yet - my spare time is spread thinly, and my paying work involves D1 primarily currently.
I would ideally like to consider trying to implement a D1/D2 plugin base class which provides a DSL for plugins to use that handles the D1/D2 differences under the hood, but I'm not sure how feasible that is.
The text was updated successfully, but these errors were encountered:
I wonder if we can take an approach like D::P::Database, where we ended up with a shared core which is then used by D::P::Database and D2::P::Database - so the actual plugins are an as-thin-as-possible wrapper around the actual core.
May or may not work as well here, as SimpleCRUD has some hairier interactions with Dancer I believe.
I still would really really like to come up with some kind of plugin abstraction that provides the same interface for plugins running under both Dancers, so you could as a plugin author just inherit from it and use its interface, and know that your plugin will work in both - but I am struggling for time lately.
Sadly, Dancer::Plugin::SimpleCRUD is currently D1-only.
I very much want to make it work with Dancer2, but just haven't had the time to spend on it yet - my spare time is spread thinly, and my paying work involves D1 primarily currently.
I would ideally like to consider trying to implement a D1/D2 plugin base class which provides a DSL for plugins to use that handles the D1/D2 differences under the hood, but I'm not sure how feasible that is.
The text was updated successfully, but these errors were encountered: