Weave Code
Filament Revealable Field Laravel Package
codebar-ag/filament-revealable-field
A Filament field that keeps sensitive values hidden until revealed. The codebar-ag/filament-revealable-field package adds a simple show/hide toggle for passwords, tokens, API keys, and other confidential data in Laravel admin panels.
Laravel Filament Revealable Field
Frequently asked questions about Filament Revealable Field
- What is codebar-ag/filament-revealable-field used for?
- It is a Laravel Filament field for keeping sensitive values hidden until a user chooses to reveal them. It is intended for passwords, API keys, tokens, and other confidential data shown in Filament admin panels. The package adds a simple show/hide toggle instead of displaying the value in plain text immediately.
- How do I install codebar-ag/filament-revealable-field in a Laravel app?
- Install it through Composer with composer require codebar-ag/filament-revealable-field and follow the repository README for any Filament-specific setup. Because it is a Filament field package, you normally use it directly in a Filament form schema after installation. Check the README for exact namespace and usage examples.
- Which Laravel and Filament versions does this package support?
- The repository and its composer.json are the source of truth for supported Laravel and Filament versions. Filament packages usually declare constraints for Filament and Laravel, so review those before upgrading your application. If your app uses older Laravel or Filament releases, confirm compatibility in the README or test in a staging copy.
- How do I use the revealable field in a Filament form?
- Add the package's field to your Filament form schema and bind it to the sensitive attribute you want to protect. Users will see the value concealed until they trigger the reveal toggle. Check the README for the exact field class name, configuration methods, and any label or visibility options.
- Can I use it for password fields and API keys?
- Yes, the package is designed for confidential values such as passwords, API keys, tokens, and other secrets in Laravel admin panels. It keeps those values hidden by default and lets authorized users reveal them when needed. It is a display convenience, so pair it with proper authorization and access policies.
- Does revealing a value expose it in the browser or network response?
- Because the value is rendered in a Filament admin page, it is present client-side when the page loads or the field is populated. The reveal toggle controls display, not encryption or server-side access. Only load records containing secrets for users who are already authorized to see them.
- Is this field secure enough for production sensitive data?
- It helps prevent accidental shoulder-surfing and casual disclosure in the admin UI, but it does not replace Laravel authorization, HTTPS, audit logging, or secret management. Ensure Filament resources and policies restrict access to records containing passwords, API keys, or tokens. Treat any value rendered in the browser as visible to the authenticated user and their tools.
- How can I test a Filament resource that uses the revealable field?
- Use Filament's testing helpers or Livewire tests to assert that the field appears in the form and that the reveal interaction behaves as expected. Keep tests focused on authorization and visibility rules for the sensitive attribute, not just the toggle UI. Review the package README for any specific testing notes.
- Are there alternatives to filament-revealable-field for hiding sensitive data?
- Alternatives include Filament's built-in password or text input fields, a custom Blade component with Alpine.js, or a package that provides a masked reveal interaction. The best choice depends on whether you need a simple show/hide toggle or stronger secret-handling controls. This package is focused on the Filament field experience rather than full secret management.
- Is codebar-ag/filament-revealable-field actively maintained?
- Review the GitHub repository for recent commits, releases, and open issues before adopting it. Check its Composer constraints and test it against your Laravel and Filament versions in a staging app. For long-term projects, also consider whether you can maintain a small custom field if the package stops receiving updates.
Weaver
How can I help you explore Laravel packages today?