Aetherupload Laravel Laravel Package

Getting Started

• Install/update with composer require ... (or composer update to pull v2.0.9), then run the package migrations/publish commands only if the README requires them.
• Look first at the package README, the published config file, and the service provider. For v2.0.9, check the new route middleware config keys and the simplified validation entry point.
• Register any new middleware alias in bootstrap/app.php (Laravel 11+) or app/Http/Kernel.php (older Laravel), following the package docs.
• First practical use case: attach the package’s route middleware through config or route groups, then use the simplified validation method in a controller/form request to validate package input.

Implementation Patterns

• Configure middleware once at the package/config level for consistent behaviour, then override per route group where needed.
• Prefer route-group middleware for package routes:

  Route::middleware(['package.basic'])->group(function () {
      // package routes
  });
  

• Use the new config options to centralize middleware enablement rather than hard-coding middleware names in many route files.
• Adopt the simplified validation method in new code first; keep existing validation flows unchanged until tests confirm equivalent behaviour.
• For integration, combine middleware config with Laravel’s standard auth/throttle middleware and verify ordering with php artisan route:list -v.
• In tests, assert both middleware behaviour (blocked/allowed requests) and validation outcomes, especially for edge cases that the simplified method now handles.

Gotchas and Tips

• Run php artisan config:clear after changing package middleware config; cached config can hide new v2.0.9 options.
• Middleware ordering matters: authentication/session middleware should usually run before package route middleware.
• Confirm the middleware alias is registered before referencing it in routes or config.
• The simplified validation method may change method signatures or default messages; review existing custom validation and form requests before upgrading.
• Check whether v2.0.9 changes route registration or middleware application for existing package routes; test route names, prefixes, and groups.
• Use route:list -v and request tests to debug middleware application rather than relying only on config inspection.
• Extension point: add custom middleware around the package’s basic middleware if you need project-specific authorization or logging without forking package routes.