- How do I install thelan/validator-pizza in a Laravel app?
- Install it with Composer using composer require thelan/validator-pizza. Laravel versions with package auto-discovery will register the service provider automatically; on older versions, add the provider manually if the package docs require it. You can then use the rule directly in your validation rules.
- How do I use validator.pizza as a Laravel validation rule?
- Add the package's rule to an email field in your rules array, whether in a controller or a Form Request. It plugs into Laravel's familiar Validator API, so you can combine it with required, email, and other rules. The rule calls validator.pizza to check the address and returns a validation failure when the API rejects it.
- Does thelan/validator-pizza support Laravel 10 and Laravel 11?
- Check the package's composer.json and Packagist releases for the exact Laravel constraints. Composer will resolve the correct version for your framework, and Laravel package auto-discovery handles registration on modern releases. If you are on an older Laravel version, confirm provider registration and PHP compatibility before adopting it.
- How do I customize the validation error message for validator.pizza?
- Define a custom message for the rule in your validation messages array or in a Form Request's messages method. The package uses Laravel's normal validation message pipeline, so the same overrides you use for built-in rules apply. If the package ships default text, you can replace it with wording that fits your product.
- Can I test Laravel validation with validator.pizza without making real API calls?
- Use Laravel's HTTP fake helpers to stub responses from validator.pizza instead of calling the live API in tests. That keeps tests fast, deterministic, and independent of network availability. Assert both passing and failing API responses so your validation paths are covered.
- What happens if validator.pizza is down or slow in production?
- Because the rule depends on an external HTTP service, production requests can be affected by latency, rate limits, or validator.pizza outages. Configure sensible timeouts and consider caching results or failing open or closed based on your risk tolerance. Monitor failures so email validation does not block legitimate signups unexpectedly.
- Does validator-pizza work with Form Requests and the Validator facade?
- Yes. The package is designed as a Laravel validation rule, so it works anywhere the Validator API is used, including Form Requests, controllers, and manual validator instances. You add it to the rules array just like a built-in rule. This keeps Form Request classes readable instead of embedding custom API logic inline.
- How do I configure timeouts or the API endpoint for validator.pizza?
- Look for a published config file or environment variables in the package documentation for endpoint, timeout, or HTTP client options. If the package exposes extension points, you can bind a custom client or rule implementation for special cases. Keep defaults unless you need to point at a proxy or tune timeouts.
- What are alternatives to thelan/validator-pizza for disposable email validation in Laravel?
- Alternatives include Laravel's built-in email rule, DNS or MX record checks, disposable-email blocklists, and other email verification APIs. Choose based on whether you need syntax validation, deliverability checks, or disposable-domain detection. Thelan/validator-pizza is convenient when you specifically want validator.pizza results inside Laravel validation.
- Is thelan/validator-pizza maintained and safe for production use?
- Review the GitHub repository for recent commits, open issues, releases, and compatibility with your Laravel and PHP versions. A small package can be stable even with infrequent releases, but check that its dependencies and API usage are current. For production, pin a known version and test upgrades in staging.