- How do I install deligoez/tckimlikno in a Laravel app?
- Install it with Composer using composer require deligoez/tckimlikno. Laravel's package auto-discovery registers the service provider, so no manual provider entry is normally needed. Publish the config file only if you need remote NVI verification or custom validation messages.
- Does deligoez/tckimlikno validate TC Kimlik No locally or call the NVI service?
- The package performs local checksum verification and provides helpers to generate valid test numbers without external APIs. It also documents an optional remote NVI verification path, which depends on an external service. For most form validation, local checksum validation is the low-risk, high-throughput option. If you enable remote checks, plan for latency, rate limits, and service downtime.
- Is deligoez/tckimlikno compatible with Laravel 12?
- Yes. Version 5.1.0 explicitly adds Laravel 12 compatibility, which removes a key blocker for teams upgrading. Confirm your PHP version meets Laravel 12's PHP 8.2+ requirement and check the package's composer constraints. Run your application test suite after updating the Composer constraint to ^5.1.
- What PHP and Laravel versions does deligoez/tckimlikno v5.1.0 support?
- v5.1.0 targets Laravel 12 compatibility, and Laravel 12 requires PHP 8.2 or newer. The package's composer.json is the authoritative source for the exact PHP and Laravel constraints, so verify it before adopting. If you are on an older Laravel version, stay on a compatible package constraint rather than forcing ^5.1.
- How do I use the TC Kimlik No validation rule in a Laravel form request?
- Add the package's validation rule to your form request or validator rules array using the documented rule syntax. The rule integrates with Laravel's standard validation flow, so failures appear as normal validation errors. Test with known valid and invalid numbers, including leading zeros, wrong length, and checksum edge cases.
- Can I generate valid Turkish Identification Numbers for testing with this package?
- Yes. The package includes helpers for producing valid test TC Kimlik numbers without calling an external API. This is useful for factories, seeders, and automated tests where you need checksum-valid values. Generated numbers are for testing and should not be treated as real citizen data.
- What happens if the remote NVI verification service is unavailable?
- Local checksum validation is unaffected by NVI outages because it runs inside your application. Remote verification depends on an external service, so you should expect possible latency, rate limiting, timeouts, and downtime. Implement explicit timeout and fallback behavior, and avoid synchronous remote checks in high-throughput request paths unless the business requirement justifies it.
- Is deligoez/tckimlikno suitable for KVKK-compliant handling of Turkish ID numbers?
- The package can validate and generate TC Kimlik numbers, but KVKK compliance is an application-level responsibility. If you enable remote NVI verification, review whether IDs are transmitted to a third party, how they are logged, and what retention and consent rules apply. Prefer local checksum validation where it meets your requirements, and avoid logging full ID numbers unnecessarily.
- How do I migrate from v5.0.0 to v5.1.0 of deligoez/tckimlikno?
- The v5.0.0 to v5.1.0 update appears non-breaking, with release notes focused on Laravel 12 compatibility. Update your composer.json constraint to ^5.1, run composer update, and execute your application test suite. No data migrations or config changes are indicated, but verify validation rule behavior on your Laravel version.
- Is deligoez/tckimlikno actively maintained and safe for production?
- The package is small, focused, and stable, with v5.1.0 being a compatibility release rather than a feature expansion. It is community-supported with no commercial SLA, and the main long-term risk is reliance on a single maintainer. For production, pin the version, monitor releases, and be prepared to fork or replace the package if maintenance stalls. Local checksum validation carries low technical risk; remote NVI checks add external-service risk.