Smart Api Bundle Laravel Package

Product Decisions This Supports

• API contract evolution: v1.1 adds a default option in request rules, letting teams decide per field whether missing request values should fail validation or fall back to a default. This supports backward-compatible API changes, optional fields, partial updates, and versioned payloads without custom request boilerplate.
• Strict vs lenient endpoints: The $throwOnUndefined flag lets PMs define whether undefined request parameters should throw or be removed. This is useful for public APIs, internal transition periods, and endpoints with different compatibility guarantees.
• Centralized input normalization: Normalizers now run before validation, so canonicalization, trimming, casting, and cleanup can happen consistently before rules execute. This reduces duplicated sanitization logic and improves data quality across endpoints.
• Predictable processing behavior: Processors run in the same order defined in the validation map, making request pipelines deterministic and easier to test, debug, and document.
• Build vs buy: For Laravel/PHP request validation, this package can replace custom middleware, request classes, and ad hoc validation helpers for common API and form workflows.
• Roadmap prioritization: Teams can ship features that depend on flexible request semantics—defaults, strictness controls, normalization, ordered processing—without building bespoke validation infrastructure.

When to Consider This Package

• You are building Laravel/PHP APIs or form-heavy applications with many request validation points.
• You need configurable handling of missing request fields: fail fast with an exception or apply defaults.
• You need per-endpoint or per-request control over whether undefined parameters are rejected or removed.
• You want normalization to happen consistently before validation.
• You need deterministic processor ordering for request-side side effects or transformations.
• You want to reduce custom validation/middleware code and standardize request handling conventions.

Look elsewhere if the application is not Laravel/PHP, if you require full JSON Schema/OpenAPI-native validation, or if the package lacks sufficient documentation, test coverage, security review, and maintenance signals for production use. Because this is a v1.1 release, validate maturity, upgrade policy, and long-term support before broad standardization.

How to Pitch It (Stakeholders)

Executives: This package reduces custom request-validation code and helps teams ship APIs faster with more consistent input handling. v1.1’s configurable defaults and strictness controls support gradual API evolution and lower the risk of breaking clients when payloads change.

Engineering: v1.1 adds practical request-pipeline controls: per-rule defaults, a $throwOnUndefined strictness flag, normalization before validation, and ordered processor execution. These features reduce boilerplate, make request behavior explicit, and improve testability. Recommend a pilot on one API surface, document strict/lenient conventions, add tests for defaults and undefined-field behavior, then standardize where the package’s maturity and support model fit production needs.