A few remarks:

• Don't require laravel/framework, composer warns about it, you would not want to end up with 2 installations of the framework. Require laravel/support instead. Or neither, since it wouldn't make sense running it outside Laravel.
• Although it works, you package namespace lacks a vendor. For example, Laravel's components are Illuminate\Auth or Illuminate\Database. This allows for the existence of other Auth and Database classes next to each other. Instead of a Vendor\Package\Class namespace, you have a Package\Class namespace. Better would be something like GaryGreen\PrettyRoutes_Classname_
• Why do you use middleware to overrule a request instead of providing a route and controller? With a route, a user could add additional middleware (such as authorization, I don't want everyone to see the routes).
• If you use something like StyleCI with the Laravel preset, your code will be styled the same as the Laravel codebase, which looks pretty.

I am having this exception while visiting /routes:

Call to protected method Illuminate\Routing\Route::controllerMiddleware() from context 'Illuminate\View\Engines\PhpEngine'

This problem is ocurring because controllerMiddleware is a protected method and is being called out of context in routes.blade.php view file on line 66.

I've followed the installation instructions, but nothing happens (composer goes through fine, I've added the entry to the providers array). I don't think the package itself is getting registered with laravel (as a test I put a simple Log command which never gets called in any of the code relating to this). When I run the vendor publish command, nothing happens (ie gives message: Nothing to publish for tag [].) Am I missing something? EDIT: using Laravel 5.1

I get InvalidArgumentException error when I run composer require garygreen/pretty-routes.

➜  pyrocms php artisan -V
Laravel Framework version 5.1.43 (LTS)

➜  pyrocms composer require garygreen/pretty-routes


 [InvalidArgumentException]
  Could not find package garygreen/pretty-routes at any version for your minimum-stability (stable). Check the package spelling or your minimum-stability


require [--dev] [--prefer-source] [--prefer-dist] [--no-progress] [--no-update] [--update-no-dev] [--update-with-dependencies] [--ignore-platform-reqs] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--] [<packages>]...

With a lot of routes, it would be handy to be able to easily see where a route is defined. I'm not sure if that's possible in this package, but if so it'd be pretty slick. The screen would be pretty cluttered as is, so perhaps a tooltip/title tag to display this would make sense.

If you think this is a good idea, and can point me in the right direction, I'd be happy to take a crack at a PR for it.

• Updated bootstrap to 4.0.0 final version.
• Added a new dark mode customizable in config file in order to care our eyes.
• Added possibility to custom route name in config file.
• Change "tag" css class to "badge".

I have tried to use pretty routes with PyroCMS. It's almost native Laravel and other soft for Laravel works fine with it.

I have caught an exception:

Please, rename file to .html and open in browser.

This is an automated pull request from Shift to update your package code and dependencies to be compatible with Laravel 9.x.

Before merging, you need to:

• Checkout the l9-compatibility branch
• Review all comments for additional changes
• Thoroughly test your package

If you do find an issue, please report it by commenting on this PR to help improve future automation.

If an deprecated label is set on a method, only its line will be crossed out. If the deprecated label is set on the class, then all its methods will be crossed out.

For example:

namespace App\Http\Controllers\Api\V1\Master;

/** @deprecated */
class BookingServicesController
{
  public function index()
  // ...
}

class BookingOrdersController
{
  /**
   * @deprecated
   */
  public function items()
  // ...
}

Result:

Hi, I have an idea which I want to try out (and create a pull-request afterwards maybe). But I'm not sure, how to do this. If I fork your project, how can I get it into another Laravel project to see my changes in action? Do I have to put it to packagists? Please help me out? :)

If you use Route::any A Route::options() Is created.

Which will throw error in view file on Line number 57.

 @foreach (array_diff($route->methods(), config('pretty-routes.hide_methods')) as $method)
    <span class="tag tag-{{ $methodColours[$method] }}">{{ $method }}</span>
@endforeach

Because $methodColours doesn't have key for 'OPTIONS'.

To solve that i've created 'OPTIONS' key which allots default class for tag coloration.

Hi,

Installed this package on lumen. Do you have any plan to make this package can be support on lumen ? Error that I get about router. Router laravel and lumen quite different .. need to enhance if want support on lumen too.

I am thinking of sending a PR which will add 1+ columns which will spit out view name that is being returned from the controller action.

Could that be useful?

I am using laravel 5.2, Installed the package,

Put the PrettyRoutes\ServiceProvider::class, above app server providers and visited /routes and its showing me

FatalThrowableError in ControllerDispatcher.php line 110:
Call to undefined method PrettyRoutes\PrettyRoutesController::getMiddleware()

Whats missing ?