Yes. It would either be in MyApp::Model::Dice or *much* better in a Games::Dice module that has nothing to do with MyApp and is used via model glue like Catalyst::Model::Adaptor.
I am trying to write a reply to your original post but it’s pretty long and I might not get it done.
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |
It beats the crap out of 100 undecorated function calls and use|require statements sprinked all over the place and even embedded in the templates with contorted logic to surface instead of just being in [% c.model("WhatWhat").call %] and then something impossible to repurpose, let alone trivially change, with a simple back end swap. c.uri_for() might seem gratuitous too if you’ve never grown an app that needed testing, flexible deployment, or midstream changes that could otherwise be trivial. :P
| [reply] [Watch: Dir/Any] [d/l] [select] |