- Calgary, Alberta, Canada
- https://nu.hyperboreal.zone/
-
meow
- Joined on
2022-11-25 -
-
$self to more descriptive names depending on where it gets used
$_set in namespace CharmBoard::Model::Schema::Set to $set
$self to more descriptive names depending on where it gets used
$_set in namespace CharmBoard::Model::Schema::Set to $set
I should clarify why: $set inherits from the ResultSet the given sub is a part of, so it's not a private, subroutine-only variable.
$_set in namespace CharmBoard::Model::Schema::Set to $set
Should probably run on index too, since that will effect listing of userclass-restricted forums (once that feature is implemented)
And before even calling $self->session_validate there should…
I guess destroying a session if its invalid is pretty straightforward, and session creation should only happen once. So maybe a Model that just does the database part of things should suffice?
No yeah, a CharmBoard::Controller::Session doesn't make sense actually when I think about it harder, knowing what I know about what the Controller namespace is even used for. So Util namespace…
...Or the other option would be putting it in CharmBoard::Util::Session. I think I need to learn more about how MVC architecture works, I guess.
Looks like things in the Model namespace aren't allowed access to HTTP request data directly, so this may have to actually be split into two modules, CharmBoard::Controller::Session for the…
CharmBoard::Model::Session