- What is radebatz/type-info-extras used for?
- It provides extra resolvers for symfony/type-info, helping reflection- and docblock-based type extraction handle more PHP constructs and libraries. It is aimed at tooling, schema generation, and validation that needs richer type metadata. It is not a Laravel package and does not add Laravel-specific type handling.
- Does radebatz/type-info-extras work with Laravel?
- Not natively. Laravel does not use Symfony's type-info component by default and relies on PHP native types and Illuminate helpers instead. You would need to manually add symfony/type-info and wire the resolvers yourself, which the assessment rates as low feasibility.
- How do I install radebatz/type-info-extras in a Laravel application?
- There are no documented Laravel integration steps. Composer installation would also require symfony/type-info, which is not part of Laravel's standard dependency set. Expect custom wiring and possible dependency conflicts rather than a Laravel service provider or config publish flow.
- Is radebatz/type-info-extras compatible with Laravel 10 or 11?
- Compatibility is not documented. Laravel 10 uses Symfony 6.x components while the package's assessment notes Symfony 7.x claims, so Laravel 10 is likely to hit Composer conflicts. Even on a Laravel version with Symfony 7 components, the package remains non-native and requires manual wiring.
- What PHP constructs does type-info-extras add support for?
- The package adds extra type-info resolvers for more PHP constructs and libraries so type extraction works in more cases. The provided overview does not list every resolver, so check the repository README for the exact supported constructs. It extends Symfony type-info rather than replacing Laravel's native type system.
- Do I need symfony/type-info to use radebatz/type-info-extras?
- Yes, the package is described as extras for symfony/type-info. It extends that component's resolver system, so symfony/type-info is the underlying dependency. Laravel projects do not include it by default, which is a key integration hurdle.
- Why use Symfony type-info in Laravel instead of native PHP types or spatie/type-utils?
- In most Laravel applications, native PHP 8+ types and Illuminate helpers are sufficient, and spatie/type-utils is a more Laravel-adjacent option for type utilities. Symfony type-info becomes relevant mainly if your tooling already depends on that component and you need its resolver ecosystem. For a standard Laravel app, adding it creates extra dependencies without a clear native benefit.
- Is radebatz/type-info-extras maintained and production-ready?
- The assessment flags high technical risk: zero dependents, minimal activity at about 3 stars, and a release dated 2026-03-06 that was noted as future-dated at review time. Those signals suggest experimental or abandoned status. Treat it as unproven for production Laravel applications until you verify recent commits, issues, and release history.
- Can type-info-extras help with schema generation or validation in Laravel?
- It can provide richer type metadata for tooling that consumes Symfony type-info, which may indirectly help schema generation or validation. However, Laravel's own validation and schema tooling do not use this component by default. You would need custom integration and should confirm the metadata output matches your pipeline.
- Does radebatz/type-info-extras support Symfony 6, or only Symfony 7?
- The assessment notes Symfony 7.x compatibility claims and warns about conflicts with Symfony 6.x LTS usage. The provided context does not confirm Symfony 6 support. Verify the package's composer.json constraints before using it in a Laravel 10 or other Symfony 6-based project.