Http Method Laravel Package

Product Decisions This Supports

• Standardization of HTTP methods across Laravel/PHP applications to reduce magic strings (e.g., "GET", "POST") and improve maintainability.
• Enabling stricter type safety by replacing hardcoded strings with immutable constants (e.g., HttpMethod::GET).
• Framework-agnostic API design for reusable middleware, controllers, or services that interact with HTTP requests.
• Roadmap alignment with Laravel’s shift toward stricter typing (e.g., PHP 8.1+ features) and consistency with Symfony’s Request object patterns.
• Build vs. buy: Avoid reinventing constants; leverage this lightweight package instead of custom implementations.
• Use cases:
  • Validating incoming HTTP methods in middleware (e.g., if ($request->method() === HttpMethod::POST)).
  • Documenting API endpoints with typed constants (e.g., #[Route(method: HttpMethod::PATCH)]).
  • Supporting non-English HTTP methods (e.g., HttpMethod::CONNECT, HttpMethod::TRACE).

When to Consider This Package

• Adopt if:
  • Your Laravel/PHP codebase uses magic strings for HTTP methods (e.g., "PUT" in route definitions or conditionals).
  • You prioritize type safety and IDE autocompletion for HTTP methods.
  • Your team follows PSR-12 or similar coding standards that discourage magic values.
  • You’re building reusable components (e.g., libraries, SDKs) where HTTP method consistency is critical.
• Look elsewhere if:
  • Your project already uses a framework-provided solution (e.g., Laravel’s built-in Request methods or Symfony’s Request::METHOD_* constants).
  • You need runtime method validation (e.g., checking if a method is allowed); pair this with a validation library like symfony/validator.
  • Your team prefers string-based methods for flexibility (e.g., dynamic route handling).
  • You’re working in a non-PHP/Laravel ecosystem where this package isn’t compatible.

How to Pitch It (Stakeholders)

For Executives: "This package replaces unreliable magic strings (like 'DELETE') with typed constants (e.g., HttpMethod::DELETE) for HTTP methods, reducing bugs and improving code clarity. It’s a zero-maintenance, MIT-licensed solution that aligns with modern PHP best practices—similar to how we’d standardize on a library for logging or caching. The overhead is negligible (just a composer require), but the long-term benefits for maintainability and developer experience are significant."

For Engineers: *"This gives us:

1. No more typos: HttpMethod::GET instead of 'get' or 'GET' inconsistencies.
2. IDE support: Autocomplete and static analysis for HTTP methods.
3. Framework parity: Works seamlessly with Laravel/Symfony/PHP’s type systems.
4. Future-proofing: Supports all standard and non-standard HTTP methods (e.g., CONNECT, OPTIONS). Use it in middleware, routes, or validation logic where HTTP methods are checked. Example:

if ($request->method() === HttpMethod::PATCH) { ... }

Downside? None—it’s a drop-in replacement for strings with zero runtime cost."