This package is to add a web interface for Laravel 5 and earlier Artisan.

Hello Mr Maurice, nice job but still have some errors, and if i don't want to touch the vendor's code, i don't see how to resolve this issue, the NiceArtisanController extends the AppController . but where is this AppController, i don't see it in L5.2 How can i solve this problem ;-)

Bonjour, Pour commencer merci pour votre contribution et votre merveilleux cour sur le site du zero. Je débute avec Laravel et j'essaye d'installer votre package mais j'ai l'erreur suivante dans ma console :

E:\wamp64\www\BDHELARAVEL52>php artisan vendor:publish --tag=niceartisan:config Nothing to publish for tag [niceartisan:config].

Mon .json : { "name": "laravel/laravel", "description": "The Laravel Framework.", "keywords": ["framework", "laravel"], "license": "MIT", "type": "project", "require": { "php": ">=5.5.9", "laravel/framework": "5.2.", "laravelcollective/html": "5.2.", "bestmomo/nice-artisan": "0.4.*" },

J'ai bien ajouté Bestmomo\NiceArtisan\NiceArtisanServiceProvider::class, dans mon fichier app.php.

Et quand j'essaye d'atteindre nice-artisan : ErrorException in NiceArtisanController.php line 94: array_keys() expects parameter 1 to be array, null given

Pourriez vous m'aider à résoudre le problème s'il vous plait ?

Je vous remercie par avance

Hi,

do you plan to support Laravel 7 in the future?

composer require bestmomo/nice-artisan
Using version ^1.2 for bestmomo/nice-artisan
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for bestmomo/nice-artisan ^1.2 -> satisfiable by bestmomo/nice-artisan[V1.2.0].
    - Conclusion: remove laravel/framework v7.0.8
    - Conclusion: don't install laravel/framework v7.0.8
...

Thank you.

Tried to add console commands from another package. And it does not work.

Tried to remove entire sections of the configuration file and it does not work.

Why have a configuration file if you are not going to change what is available in the UX by using your configuration file.

color me confused.

-FT

In 0.3 and 0.4.0 in the index.blade.php view there is no check if the default value of the argument is array or string. This is fixed in version 0.4.1. As there are no other changes could you back port this in those versions?

I don't understand what is the problem exactly, it's like some data are missing or if last merge has not worked properly. In my installation, after Composer Update, I have no change of commands config file, I have to modify NiceArtisanController in vendor and change array to make it working.

except for the "migrate" command on all other migrate commands this checkbox does not change to a green hook when clicked and this makes it impossible to run e.g. "migrate:rollback" in production

I needed to customize the route for /niceartisan, to I had to create another category of settings inside commands.php. I'm not sure if it's ok to you regarding compatibility issues.

1. Installed version 1.4
2. Set up custom middleware

When I run all of the non-custom commands, run just fine.

When I click on the Customs link, I get the following error:

Illuminate\Routing\Exceptions\UrlGenerationExceptionMissing required parameter for [Route: niceartisan.exec] [URI: niceartisan/item/{class}] [Missing parameter: group]. (View: /home/vagrant/code/mysite/vendor/bestmomo/nice-artisan/views/index.blade.php) http://mysite.test/niceartisan/customs`

Laravel: 8.83.23 Nice-artisan 1.4

Hello, I did as stated in the documentation:

Created a NiceArtisan Middlware:

<?php

namespace App\Http\Middleware;

use Closure;
use Illuminate\Http\Request;

class NiceArtisan
{
    /**
     * Handle an incoming request.
     *
     * @param  \Illuminate\Http\Request  $request
     * @param  \Closure(\Illuminate\Http\Request): (\Illuminate\Http\Response|\Illuminate\Http\RedirectResponse)  $next
     * @return \Illuminate\Http\Response|\Illuminate\Http\RedirectResponse
     */
    public function handle(Request $request, Closure $next)
    {
        $user = $request->user();
        dd($request->user());
        if ($user && $user->developer == true) {
            return $next($request);
        }

        return abort(403);
    }
}

Added the middleware to the Kernel.php:

<?php

namespace App\Http;

use Illuminate\Foundation\Http\Kernel as HttpKernel;

class Kernel extends HttpKernel
{
    /**
     * The application's global HTTP middleware stack.
     *
     * These middleware are run during every request to your application.
     *
     * @var array<int, class-string|string>
     */
    protected $middleware = [
        // \App\Http\Middleware\TrustHosts::class,
        \App\Http\Middleware\TrustProxies::class,
        \Illuminate\Http\Middleware\HandleCors::class,
        \App\Http\Middleware\PreventRequestsDuringMaintenance::class,
        \Illuminate\Foundation\Http\Middleware\ValidatePostSize::class,
        \App\Http\Middleware\TrimStrings::class,
        \Illuminate\Foundation\Http\Middleware\ConvertEmptyStringsToNull::class,
    ];

    /**
     * The application's route middleware groups.
     *
     * @var array<string, array<int, class-string|string>>
     */
    protected $middlewareGroups = [
        'web' => [
            \App\Http\Middleware\EncryptCookies::class,
            \Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class,
            \Illuminate\Session\Middleware\StartSession::class,
            \Illuminate\View\Middleware\ShareErrorsFromSession::class,
            \App\Http\Middleware\VerifyCsrfToken::class,
            \Illuminate\Routing\Middleware\SubstituteBindings::class,
        ],

        'api' => [
            // \Laravel\Sanctum\Http\Middleware\EnsureFrontendRequestsAreStateful::class,
            'throttle:api',
            \Illuminate\Routing\Middleware\SubstituteBindings::class,
        ],
    ];

    /**
     * The application's route middleware.
     *
     * These middleware may be assigned to groups or used individually.
     *
     * @var array<string, class-string|string>
     */
    protected $routeMiddleware = [
        'auth' => \App\Http\Middleware\Authenticate::class,
        'auth.basic' => \Illuminate\Auth\Middleware\AuthenticateWithBasicAuth::class,
        'auth.session' => \Illuminate\Session\Middleware\AuthenticateSession::class,
        'cache.headers' => \Illuminate\Http\Middleware\SetCacheHeaders::class,
        'can' => \Illuminate\Auth\Middleware\Authorize::class,
        'guest' => \App\Http\Middleware\RedirectIfAuthenticated::class,
        'password.confirm' => \Illuminate\Auth\Middleware\RequirePassword::class,
        'signed' => \Illuminate\Routing\Middleware\ValidateSignature::class,
        'throttle' => \Illuminate\Routing\Middleware\ThrottleRequests::class,
        'verified' => \Illuminate\Auth\Middleware\EnsureEmailIsVerified::class,
        'nice_artisan' => \App\Http\Middleware\NiceArtisan::class,
    ];
}

But it seems that $request->user() is always null, even if I'm logged in with a user. Assigning the middleware nice_artisan to the /home route (instead of the auth middleware) prints the $request->user() info correctly. Maybe it is registered too early in the package?

Provide Lumen support

Feel free to use this: https://github.com/kevupton/laravel-package-service-provider

To support simple determination between lumen and laravel and then simple registering of alias. Just extend that service provider.

When you rename the application, it will break the app if you use a naming convention that includes spaces or special characters. Recommend adding a validation to strip all non available char and remove spaces to prevent future users from breaking things.

I broke the test environment I had setup and haven't tried naming the application with single string name yet to see if there's still an issue, doubtful.

Artisan command queue:retry accept array as id of failed job(s), but the NiceArtisanController command function assign it as a single variable (line 152), instead of array.

I don't know, if any other command has requirements like this, but an exception must handled in the assignation, when command is queue:retry.

Or the config file should have parameters, where the command can be setted up for this purpose.