rotexsoft/slim-skeleton-mvc-app

This is a template web-application (powered by SlimPHP), that can be extended to build more complex web applications.

slim-skeleton-mvc-app's Issues

Version 4 Documentation Updates

• The items with the following keys (errorHandler, errorHandlerClass, notFoundHandler, notFoundHandlerClass, notAllowedHandler & notAllowedHandlerClass) in the dependencies file for version 3 are no longer present in version 4 and their previous functionality can easily be implemented in \SlimSkeletonMvcApp\AppErrorHandler->__invoke(...)

• The determineRouteBeforeAppMiddleware & outputBuffering settings that used to be in the app-settings.php file in version 3 are no longer present in version 4. See https://www.slimframework.com/docs/v4/middleware/routing.html & https://www.slimframework.com/docs/v4/middleware/output-buffering.html

Make sure all Excecptions Are Handled Properly

• In the Slim 3 based version of this framework, some exceptions get handled by Slim's default exception handler even when errorHandler is set in the application. Perhaps look into a try catch in public/index.php or advise users to use an error handler that gets rendered with pure php, no templating engine.

Remove local UI Framework Assets

Remove local UI (i.e Foundation, Bootstrap etc) files and JS and CSS framework files and replace them with cdn links for those files. This will make updating the frameworks easier since it will only be links that will be changed in the template files.

• Actually just give option to include or exclude jquery
• Look into minimalist css frameworks and choose a very light weight one that can be included or excluded (eliminating the need to include stuff like Foundation, Bootstrap, Materializecss, etc. Let users switch to those if they want but make the templates and views not heavily tied to whatever lightweight css framework is chosen from below):
  • https://www.google.com/search?q=barebones+css&rlz=1C1MSNA_enCA849CA849&oq=barebones+css&aqs=chrome..69i57j0.8011j1j1&sourceid=chrome&ie=UTF-8
  • https://www.sitepoint.com/a-basic-html5-template/
  • https://www.encode8.com/css/15-tiny-but-robust-css-frameworks-for-your-next-project/
  • https://www.encode8.com/css/barebones-css-libraries-ready-for-any-project/
  • https://acahir.github.io/Barebones/
  • https://purecss.io/
  • https://github.com/pure-css/pure

Incorporate vance lucas' dotenv package for feeding environment variables to configuration files

Incorporate vance lucas' dotenv (https://github.com/vlucas/phpdotenv) package for feeding environment variables for configuration

Make Recommended Changes

Make changes recommended here https://insight.symfony.com/projects/63306d67-1814-4bdb-98dd-481efdd32aab/analyses/1?status=commit

Update Foundation UI Framework

• Update the included Foundation UI Framework to the latest version.

Add PSR-4 option to the autoload section of the composer.json file

As per #1 (comment) , there should be a psr-4 section in the composer.json file with sane defaults for namespaces for controllers and models.

The documentation (README.md) should also contain a little bit of information on autoloading classes.

Add enhanced dev server

Use Laravel as inspiration:

dev-server-router.php

<?php
$uri = urldecode(
    parse_url($_SERVER['REQUEST_URI'], PHP_URL_PATH) ?? ''
);

// This file allows us to emulate Apache's "mod_rewrite" functionality from the
// built-in PHP web server. This provides a convenient way to test a Laravel
// application without having installed a "real" web server software here.
if ($uri !== '/' && file_exists(__DIR__.'/public'.$uri)) {
    return false;
}

require_once __DIR__.'/public/index.php';

php -S 0.0.0.0:8888 -t ./public dev-server-router.php

Class autoloading

Hi,

I see Hello controller is only available as it is declared in Composer:

1. In autoload_classmap.php:
   'Hello' => $baseDir . '/src/controllers/Hello.php'

2. In autoload_static.php:
   'Hello' => __DIR__ . '/../..' . '/src/controllers/Hello.php'

But what about other - user defined - models and controllers in the application?
What is the proper way to declare them as it seems the app itself does not look for them by itself?

Add Request & Response Factories to Container

• Register two items in the container. Each of which is a factory for creating request & response objects

Add Unit Tests

• Add Unit Tests, look at how Slim and Laravel are doing it
• Look into using example in https://akrabat.com/testing-slim-framework-actions/ & https://github.com/slimphp/Slim-Skeleton/tree/main/tests for writing unit tests for actions
• The easiest approach is to run http GET & POST requests for all the routes that come with a vanilla installation of this project and verify that the returned Response has the right status code & that the return Body contains the expected elements

Improve code organization

• Eliminate redundant code and make use of new php 7.2 and 7.3 features wherever possible.
• Look at using a package like climate for cli operations.
• Use Rector and Psalm for code enhancement
• Look at vanilla laravel projects to get ideas of best practices to incorporate

Add Users Controller

Add a lean and fully functional Users controller that will perform BREAD (Browse, Read, Edit, Add and Delete) operations on Users for each application created using this framework. This implementation should not require any composer package. Just plain old PDO and sqlite.

Make this controller also support login with Google, Facebook & other popular identity providers.

https://www.codexworld.com/login-with-google-api-using-php/