At lot has changed in the last 10 years but Coocook always has been a web application based on #Perl with #CatalystFramework and #DBIxClass. These frameworks didn’t move fast but proved to be rock solid! 💪
In the meantime we integrated other components like #Bootstrap and infrastructure like #GitLab with CI and #Docker for easier development (soon: also deployment). Fast moving #Javascript libraries have caused many more problems than the mature Perl ecosystem.
In Catalyst how to proceed with the default view after calling $c->visit() to a dedicated controller with a custom view, e.g. for sending emails?
In @coocook I use this to send emails e.g. when the password is changed. We have a dedicated Controller::Email which sets $c->stash->{current_view} to View::Email and sends an email. I’ve just noticed Catalyst doesn’t reset to default view after visit(). How to do that?
I think I’ve just saved this very useful image about the Catalyst web framework for #Perl from getting lost. 💪
The flowchart explains nicely in which order/under which circumstances Catalyst calls controller methods. It was originally posted on the project wiki but the domain got lost. 😱 I regularly use the flowchart to remember or explain that logic to other devs.
I’ve just made a PR on #GitHub to link to #WaybackMachine. Posting here as a backup.
https://github.com/perl-catalyst/Catalyst-Manual/pull/10
