Skeleton MVC

Skeleton MVC (Simple php mirco-framework)

For small and simple projects, Consist of:

• MVC Architecture
• Simple Routing
• helper functions
• Validation Class
• Simple DB Class
• Features coming

Architecture

Sekeleton MVC uses MVC architecture as name suggest. MVC stands for Model-View-Controller. Model-view-controller - Wikipedia

Model:
The central component of the pattern. It is the application's dynamic data structure, independent of the user interface. It directly manages the data, logic and rules of the application.

View:
Any representation of information such as a chart, diagram or table. Multiple views of the same information are possible, such as a bar chart for management and a tabular view for accountants.

Controller:
Accepts input and converts it to commands for the model or view.

Lifecycle

• User hits url ex: - example.com/shop/show-shoes/
• Every request is sent to index.php file
• index.php files requires autoload(Composer) and global helpers(More on this later).
• $app instance is requested from CoreSkeleton::getInstance() and User Configuration class is provided as parameter
• As you can see Skeleton class is singleton hence if instance already exists it will be returned otherwise new will be created.
  • Now inside Skeleton class while creating new instance Request instance is created.
  • Request is passed down to Router class to handle.
  • Router class invokes appropriate Controllers method in the above case AppShopController's showShoes method and passes it Request instance and arguments from url in this case none.
  • Controller is where your magic lives lets say you're fetching users list from DB and displaying it. In this case User Model will handle all data fecthing and will return you a list and you can call view function and pass it users list. You can iterate over list in view and display as you want.
  • view method returns a Response instance which you can return from controller.
  • Now we are back at router class which will return response back.
  • Now we are in Skeleton class which will assign response to property.
  • Now in index.php sendResponse() is called on $app instance which sends appropriate headers and status code alongside with content which is sent back to browser.

Now you understand how framework handle this all. Below is Documentation for each class and some examples to get you started on development.

Directory Structure

• YourApp
  • App: Your code
    • Controllers: All Controllers
    • Model: All Models
    • View: All views
    • Config.php: User config class
  • Core: Framework's code
  • public: Exposed to the web
    • index.php: App's starting point
    • .htaccess: Reroutes all request to index.php
    • assets: All static assets like css/js lives here
  • storage: Compiled views, uploaded documents, etc.
  • vendor: Composer's download of required libraries

Configuration

Altough most framework follows convetion over configuration user configuration is required for DB params and view path, etc.

User configuration lives inside your App directory in Config Class. Opening this file you'ld see Config class extends BaseConfig(CoreConfig) which is internally defined in Skeleton. Most of all configuration are const parmas some might be static methods.

This class is documented through comments so check it and you'll be able to figure out all configuration by yourself.

Routing

For routing conventions are used over configurations for ex:.

Imagine want to show post of 3 id route would look something like this

example.com/user-post/show-photos/3/paris

Above example have

• example.com : base url
• user-post : UserPostController controller (CamelCase with Controller name appended)
• showPhotos : showPhotos method (studlyCaps)
• 3, paris : anything after method name are passed as an argument to the method

so above controller class will look like

<?php

namespace AppControllers;

use CoreRequest; 

class UserPost {

    public function showPhotos(Request $request, $id, $location) {
        # $id= 3 and $location= paris
        return view('photos.show', [
            'id' => $id,
            'location' => 'paris'
        ]);
    }
}

But you may ask what about /, /about, etc. routes?

These routes are automatically routed to default_controller(can be changed in Config) default is SiteController and / action is default to index method which can be changed in config also.

You can also notice CoreRequest object being passed as first argument always. It contains various helpers for request(more info in Request section).

Request

Request is treated as object. It will passed by deafault to every controller's method as first Argument and other params will be passed after it in the sequence. ex:

For URL example.com/user-post/show-photos/3/paris

<?php

namespace AppControllers;

use CoreRequest; 

class UserPost {

    public function showPhotos(Request $request, $id, $location) {
        # $id= 3 and $location= paris
        return view('photos.show', [
            'id' => $id,
            'location' => 'paris'
        ]);
    }
}

Here are some handy methods provided by Request Object to you.

/* Check Method of request */
$request->isGet();
$request->isPost();

/* 
How to get superglobals

These methods if provided returns specific field or entire array if no parameters are passed.
If field does not exits null is returned
*/
$request->query('field'); // For GET
$request->input('field'); // For POST
$request->server('field'); // For SERVER
$request->files('field'); // For FILES
$request->all(); // For FILES and POST merged

Response

Response which need to be sent to the browser can be achieved by

view('viewpath', $data = []); // viewpath ex. phtots.show for Views/photos/show.php
view(['header', 'content1', 'content2', 'footer'], $data = []); // array alternative
json($data = [], $options, $depth = 512); // Same as setting header("Contetnt-Type: text/json"); and using json_encode()

Validation

Validation is inspired by laravel and few basic and most used rules are provided.

$errorMsgs = CoreValidator::validate($request->all(), [
    "name" => ["required", "max:30"],
    "mobile" => ["required", "digits:10"],
    "photo" => ["required", "image:image/jpeg", "max:100"],
]);

Messages generated by framework are simple and you can customize those inside Config file. Ex.

public static function getMessage($rule, $field, $params, $messages = [])
{
    $messages = [
        "required" => "Hmm... plz get the $field filled :)"
    ];
    return parent::getMessage($rule, $field, $params, $messages);
}

In above example required message will be custom one.

Available Rules are:

required

Fails if field is left empty as per php's empty() function.

string

Must be a string value.

digits:size

Must be numeric or numeric string value with given size, if size not given simply check as numeric value

boolean

True for Yes, No, yes, no, true, false, 0, 1 otherwise false

confirmed

Request data must contain field with same name with _confirmation suffix. Ex: if used on password it would check for password_confirmation field

email

Whether it's a valid email ID or not.

file

Check whether it's a valid Uploaded file or not

image:allowed_mime_types,...

Check whether it's valid image or not. Allowed Types by default : image/jpeg, image/gif, image/png, image/webp, image/svg+xml, image/bmp.

date

Whether or not it's valid date passed through strtotime() function

date_equals:date

Check whether both date are equal or not

date_after:date

Check whether user date comes after the given one.

date_beofre:date

Check whether user date comes before the given one.

different:field

Field under validation and given one must have different values.

same:field

Field under validation and given one must have same values.

present

Field under validation must be present can be null or empty.

max:size

Maximum size rule. For

Number: number must be less than or equals to the size.

String: length must be less than or equals to the size.

Array: Count of elements must be less than or equals to the size.

Uploaded file: filesize must be less than or equals to the size.

min:size

Minimum size rule. Constraint same as max:size rule.

Database

Set your database credentials and db type in Config file. Then you can always get the connection by calling:

$conn = CoreDatabase::getConnection(); // PDO instance

Model

Model is where your business would reside, which does include DB related logic also. That's why few handy methods are provided:

// suppose
class User extends Model { /* Empty */ }

$user = new AppModelsUser();
$user->find($id, columns = ['*'], $fetchStyle = PDO::FETCH_BOTH ); // Get single row
$user->all(columns = ['*'], $fetchStyle = PDO::FETCH_BOTH ); // get all rows
$user->insert($data); // As associative array of column name and values
$user->update($id, $data); // $id to be updated with $data
$user->delete($id); // Row to delete with $id

Model will infer the name of table as snake_case plural form of you class name. so in above case for User class would be users same way AppData would be app_data and gallery would be galleries. You can define your own name by overriding $table property, same way $id is considered default primary key and can be overriden too.

class User extends Model
{
    protected $table = "my_table";    
    protected $id = "tbl_id";    
}

Anything complex than this you've to do querying by yourself. Ex:

use CoreModel;
use CoreDatabase;

class User extends Model
{
    public function deleteByName($name)
    {
        $sql = "DELETE FROM $this->table WHERE name=?";
        return Database::getConnection()
            ->prepare($sql)
            ->execute([$name]);
    }    
}

Also to get last insert id you can do Database::getConnection()->lastInsertId().