Releases: volter9/mini_framework
Routing fix
2.0.0
There's a lot of changes happened to the mini_framework. The brief list of these changes:
- Namespaces for each module (almost every module) were added.
- Global refactoring (code readability improvement).
- Each API module can be initiated via
loader\api($module_name, $array_arguments). - Most of modules covered by unit-tests
Router module changes:
- Router now only accepts
callable's as second parameter. - Actions were added (helpers for routing)
- Function
routewas renamed torouter\map
View module changes:
- Views now can be rendered from
view.directoryinstead ofview.directory/template_name/htmlifview.templateis not specified in config - Function
view\capturewas added
Other modules changes:
- Validation returns only error codes instead of localized messages (
validation\validate_fieldnow can be used to validate only one value). - Pagination was improved (bug were fixed)
- Events' function
eventswas removed, the functionevents\bindnow is the container i18nfunction was renamed toi18n\getload_languagefunction was renamed toi18n\loadload_modelfunction was renamed toloader\modeland works differently (because of namespaces)
Config specification changes:
templateskey in config is renamed toviewdatabasekey is renamed todbroutingkey was removed (thereforebase_urlandsymbolskeys were removed)
Finally, in detail review of changes:
Namespaces
Namespaces were introduced to the 2.0.0. Now each module, controller and models should be contained in the namespace. Most of the API changed due to the namespace introduction (actions, loader\model).
Module API
API modules are the core modules of mini_framework. Before 2.0, modules were loaded by function load_system and initialized in system_load function. Now, modules are loaded and initialized inside of loader\system and to every init function of every module (if init function exists) passed an array of settings from config on app\boot.
If you need to initialize module manually, by invoking loader\api, you should also provide an array with expected keys and values.
Router changes
Because of namespaces it became harder to parse file:action second argument to route function. Instead of parsing, I introduced "actions".
Actions are basically functions which returns a closure which lazy-loads controller actions (functions in separate files). There's brief example:
router\map('GET page /page/:num', actions\controller(
'view', '\actions\page',
'app/actions/page'
));If this route would be found and executed, actions\controller would lazy load app/actions/page.php, and invoke \actions\page\init (if it exists) and \actions\page\view.
1.2.3
- Internal modification of router therefore allowing to write different response processors
auto_dispatchingfixautoload.filesconfig key fix (which resulted to error if the key is missing in array)autoload.modulesconfig key was added – now you can pass modules names (in mini_framework) which you want to load instead of predefined ones- In each module there was added
@require's to identify which other modules are dependencies of current module (most of them are dependent uponstorageandarray)
1.2.2
- Pagination was fixed and broken
view_pathnow also accepts absolute path (it means that you can use any file, and not only views in templates)preparerenamed todb_prepare- DB now can accept raw DSN or DSN attributes ('key' => 'value' turns into 'key=value;' in DSN)
- New DB function
db_query, which just performs a database query and returnsPDOStatement - Loader isn't dependent on
repoor any other component (however, functionsload_app_fileandload_apineed corresponding constants:MF_APP_DIRandMF_API_DIR)