Weave Code
Values Laravel Package
formapro/values
A lightweight Laravel/PHP package for working with typed values and value objects. It provides a clean, expressive API to encapsulate data, validate inputs, and keep domain logic consistent, reusable, and easy to maintain without unnecessary boilerplate.
formapro/values is a lightweight PHP library for modelling domain data with typed value objects. It helps replace loose primitives with meaningful, validated types, making code easier to read, test, and maintain while staying framework-agnostic and easy to use in Laravel or any PHP project.
- Encapsulate validation and normalization in reusable value objects
- Improve type safety and reduce primitive obsession
- Keep domain models expressive and self-documenting
- Dependency-light API with straightforward integration
- Consistent handling of scalar and structured values
Frequently asked questions about Values
- What is formapro/values used for in a Laravel application?
- formapro/values is a general-purpose PHP library for typed value objects that wrap scalars, arrays, dates, and objects with validation, null-safe access, equality checks, and simple conversion. In Laravel it can help legacy array-heavy code gain object semantics without losing array-style access. It is not framework infrastructure and overlaps with Collections, typed DTOs, readonly classes, enums, and spatie/laravel-data.
- How do I install formapro/values with Composer?
- Install it with Composer using composer require formapro/values, then confirm the package constraints against your PHP version. The package is not expected to ship a Laravel service provider or configuration file. Because the last release is from 2019, run the install in a compatibility spike before adding it to production requirements.
- Does formapro/values require a Laravel service provider or configuration?
- No Laravel service provider or configuration surface is expected from this package. It is a plain PHP utility rather than Laravel-specific framework infrastructure. Integration effort should focus on PHP compatibility, serialization behavior, and whether its array-access and mutation semantics fit your application.
- Does formapro/values support Laravel 10, Laravel 11, and PHP 8.x?
- There is no evidence in the assessment that formapro/values has been validated on Laravel 10, Laravel 11, or PHP 8.x. The last release date is 2019, so PHP 8 compatibility is a specific risk that must be proven with tests. Run a time-boxed spike against your exact PHP, Laravel, PHPUnit, static analysis, queue, and cache matrix before adoption.
- Is formapro/values maintained and safe for production Laravel code?
- The package shows high maintenance risk: a 2019 release, low star count, unknown repository provenance, and no evidence of active support. MIT licensing lowers legal risk and allows an internal fork, but a fork creates ongoing ownership cost. Treat production use as conditional and only after compatibility and behavior tests pass.
- Can formapro/values replace Laravel Collections or typed DTOs?
- It should not be treated as a default replacement for Laravel Collections, typed DTOs, readonly classes, enums, or spatie/laravel-data. It is better suited to narrow legacy areas where associative arrays cross service boundaries and you want object semantics with array-style access. New Laravel code should generally prefer native typed value objects and Collections.
- Are formapro/values objects immutable, and how are nulls and missing keys handled?
- The assessment does not establish clear immutability guarantees, so you must test mutation, nested values, nulls, missing keys, and type coercion explicitly. Hidden array and object semantic differences are a known risk with this kind of hybrid value structure. Document the behavior in an application-owned wrapper before letting it spread through call sites.
- How does formapro/values serialize for queues, cache, sessions, Eloquent casts, and API responses?
- Serialization behavior is not confirmed by the assessment and should be tested for queues, cache, sessions, Eloquent casts, and API resources. There are no known Laravel integration patterns in the package, so do not assume it works cleanly with framework serialization. Keep package-specific types behind adapters or app-owned value objects to preserve an exit path.
- How should I test formapro/values before using it in a Laravel project?
- Run a time-boxed compatibility and behavior spike on your target PHP and Laravel versions. Add tests for construction, access, mutation, nested values, nulls, missing keys, validation, equality, and serialization across queues, cache, sessions, Eloquent casts, and API responses. Also check PHPStan or Psalm impact and transitive dependency or autoload conflicts.
- What are the best alternatives to formapro/values for Laravel value objects?
- Native Laravel and PHP options include Collections, typed DTOs, readonly classes, enums, and packages such as spatie/laravel-data. These are safer defaults for greenfield Laravel applications and usually offer better static-analysis and framework integration. Consider formapro/values only for narrow legacy array-heavy modules, with a planned migration path to native alternatives.
Weaver
How can I help you explore Laravel packages today?