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
As per discussion with Nath and Simon, it would be awesome to have some sort of a flag for createModel that will turn soft-delete on for specific models
The text was updated successfully, but these errors were encountered:
I took a quick run at this. I moved away from the flag in createModel option because I figured the soft deletion route was kinda useless without corresponding filtering in the get methods.
Also, should the soft deletion take place within the controller or the model? The controller seemed like the more natural place.
The thing I really dislike about the current implementation, though, is that the controller methods are duplicated from the controller util lib into the actual controller template. Before this is useful those method overrides need to move into the controller util lib and the generator should just cause the softDelete: true flag to be passed.
hey, thanks for the attempt. i still reckon it should be a model feature though. get, query, watch could all be patched on fly, that's why we have a model factory there in the first place.
the controller layer is always an option, but i'd rather leave it the application business logic as much as possible, if we're going to keep pushing framework features in there it will become a mess way before a single line of application code lands.
so, we should at least try hard to land it in the models layer first
As per discussion with Nath and Simon, it would be awesome to have some sort of a flag for
createModel
that will turn soft-delete on for specific modelsThe text was updated successfully, but these errors were encountered: