Skip to content

[Proposal] Navigation split up by Resource #3

@ghost

Description

I am currently working on a PR which makes it possible to group the navigation by resource. To do this you need to define a @resource annotation on top of a controller which will be used as a categiory for all methods inside of the controller.

Would the @resource annotation be fine for this or should something else be used?

Controller

<?php

namespace App\Http\Controllers;

/**
 * @resource Invoices
 */
class InvoiceController extends Controller
{
    ///
}

Result
sadasd

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions