- What does wotz/filament-placeholder-input do in Laravel?
- It adds a Filament form field that lets you place read-only hint text or static content next to an editable field in a Laravel admin panel. The package is a presentation-layer UI component for Filament forms, not a data model or backend feature. Use it when editors need guidance or merge-tag hints inside a form schema.
- How do I install wotz/filament-placeholder-input?
- The technical evaluation describes installation as composer require wotz/filament-placeholder-input, followed by referencing the field class in your form schema or registering it as a plugin in the panel provider. There are no external services, credentials, or infrastructure steps involved. Confirm the exact namespace and registration pattern against the repository README before wiring it into a project.
- Which Filament versions are supported by wotz/filament-placeholder-input?
- The provided context does not state a supported Filament version range or compatibility matrix. The evaluation specifically asks whether the package proves support for Filament majors and minors, since Filament's form component contracts have changed between releases. Check the repository composer.json, CI matrix, and release notes before assuming compatibility with your panel.
- Does it work with Filament v3 and v4?
- That is not confirmed in the supplied materials; the evaluation lists Filament version support as a key open question. Filament form-field internals can differ across majors, so a package that works in one version may need changes in another. Validate against your exact Filament and Livewire versions in a spike branch before adopting.
- Can I use wotz/filament-placeholder-input inside Filament repeaters or relation managers?
- The evaluation flags repeaters, builders, nested relation managers, and modal forms as the realistic validation surface because Livewire component keys and state paths become non-obvious there. The package is described as a Filament form-field extension, so those dynamic contexts are exactly where you should test state sync. Do not assume it works in nested schemas without a hands-on spike.
- Is wotz/filament-placeholder-input safe for production use?
- The technical evaluation rates technical risk as high relative to the value delivered, driven mainly by weak trust signals: one star, zero dependents, and no known downstream field testing. It also flags an XSS surface if placeholder content is interpolated as HTML into a rich editor rather than escaped or inserted through the editor's sanctioned API. Treat production adoption as requiring your own review, tests, and possibly a fork.
- How does the package handle escaping and XSS when inserting content?
- The supplied context does not document the escaping strategy; the evaluation explicitly asks whether stored placeholder content containing script tags or event handlers can reach the rendered editor. Rich-editor injection is called out as an XSS risk if content is treated as HTML instead of being escaped or passed through a public editor API. Inspect the source and test with hostile placeholder values before exposing it to untrusted editors.
- Is wotz/filament-placeholder-input a true Filament plugin or just a field class?
- The evaluation says integration can be direct field-class reference in a form schema or plugin registration in the panel provider, but it asks whether the package is a discoverable plugin with publishable views and assets or a bare class needing manual view publishing. The README excerpt provided is empty, so that distinction is not confirmed here. Check the repository structure and service provider before planning installation.
- Is wotz/filament-placeholder-input actively maintained?
- The evaluation describes a solo-author package with one star, zero dependents, no community signal for surviving Filament minor upgrades, and a release timestamp (2026-09-15) that should be verified directly against the repository. It recommends not adopting it as a dependency of record. A safer path is to spike it, then vendor or fork it with tests and a Filament version pin, or build the equivalent custom field in-house.
- What are alternatives to wotz/filament-placeholder-input?
- The evaluation suggests a documented custom Filament Field with a Blade view and a small Alpine component, which a competent Filament developer could reproduce in roughly a day. For editor-specific needs, it also mentions filament-tiptap-editor merge tags or a first-party field as possible alternatives. Given the package's scope, building or vendoring the behavior in-house may be cheaper over a 12-month horizon.