-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: destroy routes don't redirect #502
Comments
I don't think that PR fixes the full problem described in this issue |
Oh I only read the title, will check |
Okay yeah the PR doesn't fix redirects, just the For the inheritance errors where things like For the inheritance errors where methods like |
I think that should do it yes. Nice idea to conditionally call |
Yeah I have not touched this. It is not related to #539 |
Okay, so I can start working on refactoring CRUD related controllers? |
#539 only updates (is gonna) components in |
How to reproduce
Destroy a photo-comment
Expected behaviour
on successful destroy, redirect to photo album (according to implementation)
Desirable behaviour
Instead of redirecting to album, it makes more sense to redirect to photo.
Current behaviour
destroy succeeds, but no flashnotice is shown, and no redirect takes place.
Suspected reason
the refactor in which we removed mixins, where the
model-save
util was introduced, didn't properly couple theedit
controller actions to the model save util methods (overriding theonSuccess
action in thedestroy
controller does not change the actual behaviour in themodelSaveUtil
class, becausedestroy
inherits fromedit
, not from ModelSaveUtil). There are other issues related to passingmodelSaveUtil.onSuccess
to thethen
of a promise, but after fixing those, I found the root issue being reliance on inheritance where there is none.The text was updated successfully, but these errors were encountered: