itsgoingd / itsgoingd/clockwork

Allow adding our own middleware

Open
#742 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
6k
Forks
333
Avg merge
5m
Merged PRs (30d)
1

Description

I think it would be good if we have an option to add our own middleware to clockwork routes.

Image

For example, maybe in config/clockwork.php:

<?php

return [
    // .......other configs

    'web' => env('CLOCKWORK_WEB', true),
    'web_middleware' => [], // default to empty array

    // .......other configs

below, we can add middleware:

<?php

return [
    // .......other configs

    'web' => env('CLOCKWORK_WEB', true),
    'web_middleware' => ['auth:admin', 'is_verified'],

    // .......other configs

I hope you consider this request and thank you for this amazing package👍.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with config/clockwork.php and the code that registers Clockwork routes; trace how route middleware is currently configured. Done means the requested web_middleware setting is supported, including its default empty value, and the listed middleware is applied to the Clockwork web routes.

Written by the indexing model from the issue text.

Assessment

Tech stack
laravel, php
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.