ust thinking through the refactoring and... idunno... <ul> <li> User Class/Object <ul> <li>What is the user responsible for? Their roles & permissions (essentially, a user has to provide credentials in order to prove the access they have to something.). Logging in, maybe. Registering, maybe. Profile data.</li> </ul> </li> <li> Database Class / Object <ul> <li>Responsible for all database operations across all tables. As the amount of functions grows to be hard to manage, the database class might be separated into multiple classes or multiple traits</li> </ul> </li> <li> Core Component <ul> <li>Provides an API for working with the broader user system. a website developer will call the api functions to do everything they need. On some occasions, the site developer might call upon other classes directly, but it's not supposed to. The only things to expose to the site dev is the instantiated user object (after retrieving from this component), and the apis written in this component</li> </ul> </li> </ul> It might help to think about all the things that the user app does. So: <ul> <li>Register New Users</li> <li>Login new users</li> <li>Reset password</li> <li></li> </ul> What are my primary goals with the refactor? <ul> <li>Decouple Sentinel from my app - SIMPLY create a standin for Sentinel functions, so that I can do 1-to-1 replacements in a single class when I decide to drop sentinel.</li> <li>Replace the reference to the 'sentinel' object in the user class <ul> <li>But not necessarily remove the reference to a database object</li> </ul> </li> <li>Define a logical structure that is easy to maintain</li> <li>Separate major functional pieces of the user app.</li> </ul> What is NOT a goal of the refactor? <ul> <li>Defining a class for every table in the database</li> <li>Replace Sentinel completely</li> <li>Decouple everything from each other</li> <li>Create the "perfect" architecture</li> <li>Turn the user class into a db-connected model</li> <li>Add functionality to the user class</li> <li>Add roles & permissions to the app</li> <li>Add features like replacing public files & views to the app.</li> </

Just thinking through the refactoring and... idunno...

User Class/Object
- What is the user responsible for? Their roles & permissions (essentially, a user has to provide credentials in order to prove the access they have to something.). Logging in, maybe. Registering, maybe. Profile data.
Database Class / Object
- Responsible for all database operations across all tables. As the amount of functions grows to be hard to manage, the database class might be separated into multiple classes or multiple traits
Core Component
- Provides an API for working with the broader user system. a website developer will call the api functions to do everything they need. On some occasions, the site developer might call upon other classes directly, but it's not supposed to. The only things to expose to the site dev is the instantiated user object (after retrieving from this component), and the apis written in this component

It might help to think about all the things that the user app does. So:

What are my primary goals with the refactor?

Decouple Sentinel from my app - SIMPLY create a standin for Sentinel functions, so that I can do 1-to-1 replacements in a single class when I decide to drop sentinel.
Replace the reference to the 'sentinel' object in the user class
- But not necessarily remove the reference to a database object
Define a logical structure that is easy to maintain
Separate major functional pieces of the user app.

What is NOT a goal of the refactor?

Taeluf.com