You’re browsing the documentation for v3.x.

  Click here  for earlier leaf mvc versions.

# What's new?

TIP

This section is for those who have experience with Leaf MVC 2. If you are new here, you can move to the next section.

Version 3 of leaf MVC contains a bunch of new features, some inclusions and even some breaking changes which are geared to easy integration with other libraries, as well as bettering some internal features used by leaf MVC and Leaf API.

# Normalized folder names

Leaf MVC now has normalized names for directories. Directories now use lowercase instead of the earlier pascal case.

C:.
├───app
│   ├───console
│   ├───controllers
│   │   └───Auth
│   ├───database
│   │   ├───factories
│   │   ├───migrations
│   │   └───seeds
│   ├───helpers
│   ├───models
│   ├───routes
│   └───views
│       ├───components
│       └───pages
│           └───errors
├───config
│   └───command
├───public
│   └───assets
│       ├───css
│       ├───images
│       ├───js
│       └───sass
├───storage
│   ├───app
│   │   └───public
│   ├───framework
│   │   └───views
│   └───logs
└───vendor
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

# Public directory

In earlier versions, the public directory was hardly used, however, v3 changes things a bit. Due to security and other reasons, our application root was moved to the public directory.

Note

This does not change the way you build your apps in any way.

Besides the app root in public, application assets are also now kept in the public directory as well. This is because the public directory is configured to be relative to whichever server/hosting platform or technique you are using. public will always point to your public directory.

Note

With this change, you will need to reference your assets with PublicPath

# Better configuration

Leaf MVC now includes configurations in the config folder which allows you to easily configure Leaf's features: things like cors, views, authentication and aloe's directories. Editing the configuration allows you to customize the behaviour of Leaf's features.

# Global Methods

Leaf MVC no longer comes with "self-defined" global methods. Leaf 3 now comes with functional mode which replaces the whole idea of defining functions for Leaf MVC. Leaf MVC core which is used in Leaf MVC, Leaf API and Skeleton comes in with new global functions which extend Leaf 3's functional mode.

# Leaf 3

A little obvious here, but leaf MVC 3 runs on Leaf 3. This makes it even lighter, faster and easier to work with. This also means that you have access to tons of features through modules and you won't need to worry about updating the whole framework to receive updates. You only need to upgrade a particular module.

# Modules

Some leaf 3 modules come integrated directly with Leaf MVC along with some config options.

# MVC Core

MVC core is a leaf 3 module which contains all the functionality for transforming leaf into a full MVC framework. It comes with features like controllers, models, views, factories and many more MVC specific features. It has been optimised for leaf mvc, leaf API and Skeleton to provide the best developer experience.

We really recommend that you read the MVC core documentation (opens new window)