If a new contributor forks the project and runs the tests .. then it fails .. and it suggests adding -d --update-snapshots flag with the PHP unit command.. then tests works fine.

but the problem is snapshots output file is modified and then it will be part of new PR. SO each new PR will have its own snapshot version.

Taylor just informed me that Laravel recently got except-path and has had only-path for a while, so it would probably be worth deprecating the old syntax and changing this package's flags to match Laravel's:

https://twitter.com/stauffermatt/status/1389245939106390019

Would you accept a PR to change the syntax and either drop the old syntax, or offer it as a deprecated fallback?

This PR will add 2 github actions

1. To check if the PR is following .php_cs.dist rules if not then it will apply those changes with commit message Automatically applied php-cs-fixer changes.
2. It checks if all tests are still passing when new PR is generated and also when pushed to master branch.

ParseError
syntax error, unexpected 'Package' (T_STRING), expecting function (T_FUNCTION) or const (T_CONST)

::Composer\Autoload\includeFile
E:\wamp64\www\AcodePlus\vendor\spatie\laravel-package-tools\src\PackageServiceProvider.php:14

`<?php

 

namespace Spatie\LaravelPackageTools;

 

use Carbon\Carbon;

use Illuminate\Support\Facades\View;

use Illuminate\Support\ServiceProvider;

use Illuminate\Support\Str;

use ReflectionClass;

use Spatie\LaravelPackageTools\Exceptions\InvalidPackage;

 

abstract class PackageServiceProvider extends ServiceProvider

{

    protected Package $package;   <-- error here (line 14)
 

    abstract public function configurePackage(Package $package): void;

 

    public function register()

    {

        $this->registeringPackage();

 

        $this->package = new Package();

 

        $this->package->setBasePath($this->getPackageBaseDir());

 

        $this->configurePackage($this->package);

 

        if (empty($this->package->name)) {

            throw InvalidPackage::nameIsRequired();

        }`

 

Is your feature request related to a problem? Please describe. No

Describe the solution you'd like It would be nice to have an option to see the middlewares for a route in pretty.

Describe alternatives you've considered

Additional context

When trying to run php artisan route:pretty, I get this error : ` ErrorException

Undefined array key 0

at vendor/laravel/framework/src/Illuminate/Routing/Router.php:1286 1282▕ if ($method === 'middleware') { 1283▕ return (new RouteRegistrar($this))->attribute($method, is_array($parameters[0]) ? $parameters[0] : $parameters); 1284▕ } 1285▕ ➜ 1286▕ return (new RouteRegistrar($this))->attribute($method, $parameters[0]); 1287▕ } 1288▕ } 1289▕

  Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))

`

My project use Laravel 8.5.9

composer require wulfheart/pretty_routes:^0.3.0

./composer.json has been updated
Running composer update wulfheart/pretty_routes
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires wulfheart/pretty_routes 0.3.0 -> satisfiable by wulfheart/pretty_routes[0.3.0].
    - wulfheart/pretty_routes 0.3.0 requires illuminate/contracts ^8.0 -> found illuminate/contracts[v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.


Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Just a thought here, maybe it'd nice to move the config inside the config file and let the user overwrite them if they explicitly put it in the command.

What if we have a new custom flag which will show only the routes we want

—show=tickets

it will show only routes which has tickets in it.

If you think its good i can send you a PR.

└─[$] <git:(pretty_routes*)> sail artisan route:pretty
  GET|HEAD / ..................................................... index
  GET|HEAD _debugbar/assets/javascript .............. debugbar.assets.js
  GET|HEAD _debugbar/assets/stylesheets ............ debugbar.assets.css
  DELETE   _debugbar/cache/{key}/{tags?} ......... debugbar.cache.delete
  GET|HEAD _debugbar/clockwork/{id} ................. debugbar.clockwork
  GET|HEAD _debugbar/open ......................... debugbar.openhandler
  GET|HEAD _debugbar/telescope/{id} ................. debugbar.telescope
  GET|HEAD api/user .................................................... 

   ValueError 

  str_repeat(): Argument #2 ($times) must be greater than or equal to 0

  at vendor/wulfheart/pretty_routes/src/Commands/PrettyRoutesCommand.php:161
    157▕             $method = $route["method"];
    158▕             $uri = $route["uri"];
    159▕             $name = $route["name"];
    160▕ 
  ➜ 161▕             $spaces = str_repeat(' ', $maxMethod + 6 - strlen($method));
    162▕ 
    163▕             $additionalSpace = ! is_null($name) ? 1 : 0;
    164▕             $dots = str_repeat('.', max($terminalWidth - strlen($method.$uri.$name) - strlen($spaces) - 14 - $additionalSpace, 0));
    165▕ 

      +15 vendor frames 
  16  artisan:37
      Illuminate\Foundation\Console\Kernel::handle()

do you have any idea why this happens / do you need more information about my route definitions for this problem to solve?

thanks a lot !

When I try to install it on my Laravel 7 project it shows this problem

Problem 1 - Root composer.json requires wulfheart/pretty_routes ^0.3.0 -> satisfiable by wulfheart/pretty_routes[0.3.0]. - wulfheart/pretty_routes 0.3.0 requires illuminate/contracts ^8.0 -> found illuminate/contracts[v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.