- How do I install r64/nova-dni-field in Laravel Nova?
- Install it with composer require r64/nova-dni-field and add Dni::make('DNI') to the relevant Nova resource. In the typical case there is no asset publishing or migration step. Confirm that the field renders and validates on your exact Nova version before rolling it out.
- Which Laravel, PHP, and Nova versions does r64/nova-dni-field support?
- The provided assessment suggests the package was written against Nova 1.x through 3.x on PHP 7.x, but it does not confirm an explicit support matrix or a maintained branch. Nova 4 moved to Vue 3 and raised the PHP floor, and Nova 5 continues that line, so a Vue 2 era field is the most likely breakage point. Treat rendering and validation on your target Nova, Laravel, and PHP versions as the gating experiment.
- Does r64/nova-dni-field validate DNI, NIE, and CIF numbers?
- The overview says the field adds Spanish identity document validation for DNI, NIE, and CIF values. That includes the DNI eight digits plus mod-23 check letter, NIE with X/Y/Z prefix, and CIF control character. Do not take the implementation on trust; verify it against authoritative fixtures before relying on it.
- Is validation enforced server-side or only in the Nova form?
- The assessment flags client/server validation drift as a key risk and does not confirm whether validation is enforced server-side. If validation lives only in the Vue component, API writes and imports can bypass it entirely. Add a server-side Laravel rule for compliance-adjacent identity data regardless of what the field does.
- Does the field normalise Spanish DNI input before saving?
- The assessment lists input normalisation as an unresolved question, so check whether the field uppercases values and strips separators before persisting or stores raw input. If it does not normalise, handle that in your application with a mutator or form request. Consistent storage matters for later validation and search.
- Can I use r64/nova-dni-field with Laravel Nova 4 or Nova 5?
- Compatibility with Nova 4 and Nova 5 is not confirmed in the provided material. The package's provenance suggests a Vue 2 era component, which may install cleanly but fail at render time under Nova 4 or 5. Stand up a throwaway Nova instance at your target version and test both rendering and validation before adopting it.
- What should I test before using r64/nova-dni-field in production?
- Use an authoritative fixture set covering NIE prefixes, CIF control-letter special cases such as K, L, and M, digit-versus-letter control variants, leading zeros, and lowercase input. Also test API writes and imports to confirm server-side enforcement. Pin an exact package version and record the tested Nova, Laravel, and PHP combination.
- What are alternatives to r64/nova-dni-field for Spanish DNI validation in Laravel?
- A standard Nova Text field plus a custom DniRule or well-maintained community or Symfony validator constraints delivers the checksum validation without the Vue 2 coupling. If you are not on Laravel Nova, port the validation logic into an application rule and build the input natively. This is a bounded substitution and removes the abandonment risk.
- Is r64/nova-dni-field maintained and safe to depend on?
- The assessment notes 8 stars, 0 dependents, no issue activity, and no maintainers, so there is no community canary. It is a low blast-radius leaf dependency because it touches no models, migrations, queues, or service providers beyond optional auto-discovery, but abandonment risk is real. If you adopt it, pin an exact version and consider forking into a private VCS.
- Can I fork r64/nova-dni-field or use it internally?
- Check the package license first; the assessment lists permissive licensing for an internal fork as a question to resolve. If the license allows it, fork the code into a private repository so you own it if upstream disappears. That also lets you add server-side validation and tests without waiting for maintainers.