- Does tejadong/graphql-mutation-validator-bundle work with Laravel?
- It is described as a Symfony/PHP bundle, not a native Laravel package, so direct Laravel integration is not documented in the supplied information. Laravel teams should inspect composer.json constraints, service provider requirements, and whether the bundle depends on Symfony-specific components before adopting it. Test installation in a branch against your target Laravel and PHP versions. If Symfony dependencies conflict, consider a Laravel-native validation approach instead.
- What does this GraphQL mutation validator bundle do?
- It validates GraphQL mutation inputs before resolvers execute. You can define rules and enforce schema constraints, and the package returns structured errors for invalid mutations. This helps APIs reject bad input early and behave predictably.
- How do I install the package with Composer?
- The documented distribution method is Composer, so installation would typically use composer require tejadong/graphql-mutation-validator-bundle. However, the supplied context does not include exact install steps, service-provider registration, or configuration publishing instructions. Check the repository README and composer.json for the supported package version and autoload details. Validate the install in a staging branch before production.
- What PHP versions are supported?
- The only release evidence provided is that v1.0.12 is a patch adding PHP 7.3 compatibility. The package's minimum and maximum PHP constraints are not supplied, so you must read composer.json. Do not assume compatibility with PHP 8.x or later without verifying constraints and CI coverage. PHP 7.3 is end-of-life, so modern stacks need explicit confirmation.
- Which Laravel versions are supported?
- Laravel version constraints are not supplied in the available context, and the package is described as a Symfony/PHP bundle rather than a Laravel package. There is no documented evidence of Laravel service providers, facades, or Laravel-specific configuration. Confirm support directly in composer.json and the repository documentation. Treat Laravel compatibility as unproven until tested.
- Is PHP 7.3 covered by CI?
- The release note states PHP 7.3 compatibility, but CI coverage is not evidenced in the supplied assessment. A patch claiming PHP 7.3 support should ideally be backed by automated tests on that runtime. Ask the maintainer or inspect the repository CI configuration before relying on it. Without CI evidence, validate PHP 7.3 behavior yourself.
- Should I use this package on a modern PHP/Laravel stack?
- For modern Laravel and PHP stacks, v1.0.12 adds no documented capability and may increase exposure to an unsupported runtime. The assessment recommends that modern applications should not delay PHP or Laravel upgrades to adopt this release. If you need GraphQL mutation validation, evaluate Laravel-native or actively maintained alternatives. Only adopt this package where a legacy PHP 7.3 requirement is already established.
- What are alternatives for validating GraphQL mutations in Laravel?
- The supplied context does not name specific alternatives, so avoid assuming a particular package. Laravel teams can use framework validation rules, GraphQL middleware, or dedicated GraphQL validation libraries compatible with their stack. Compare maintenance status, PHP/Laravel constraints, and test coverage. A Laravel-native approach may reduce Symfony dependency risk.
- How do I define validation rules and return structured errors?
- The overview says you define rules, enforce schema constraints, and return clear structured errors before resolvers run. Exact configuration syntax and error shape are not included in the supplied README excerpt. Consult the repository documentation for rule definitions and response formats. Validate the error contract in your API tests.
- What is the maintenance and support policy?
- The assessment notes a normal-looking patch cadence but says it is unproven from a single release note. PHP 7.3 support increases legacy maintenance burden, and the maintainer's support policy for end-of-life PHP is not documented in the supplied context. Confirm expected lifetime, security patching, and compatibility commitments with the maintainer. Plan ownership for EOL runtime risk.