Getting Started

Treat v0.1 as an early baseline release. The release notes only show a Dependabot bump for dependabot/fetch-metadata; no runtime features, breaking changes, or migration notes are documented.
Verify compatibility first from the package README and composer.json: Laravel version, Filament version, PHP version, and whether it is a Filament plugin, page, or resource package.

Install with Composer:

composer require afsakar/filament-form-maker

Inspect available publish tags before assuming names:
```
php artisan vendor:publish
```
Publish the config, migrations, and assets using the tags documented by the package.
Register the plugin/page in your Filament panel provider using the exact class from the README, then run migrations.
First use case: create a simple form in the Filament admin UI, add name, email, and message fields, publish/render it, submit it once, and confirm the submission is stored and visible in the admin.
Look first at: README, config file, migrations, Filament resources/pages, and any tests or demo app in the repository.

Implementation Patterns

Use the package as a form definition and submission layer: define forms in Filament, render them on the front end, validate dynamically, and persist submissions.
Keep a thin application wrapper around package APIs, for example a FormSubmissionService or action class. This limits coupling while the package is at v0.1.
Submit forms inside a database transaction, especially if submissions and related records are written together.
Version form schemas when fields change. Avoid mutating a live form definition in ways that make historical submissions hard to interpret.
Use Filament policies and middleware for admin-side form management, and add your own access checks for public/front-end form rendering.
If custom field types are supported, register them through the documented extension point. If not, keep custom behavior in your own wrapper rather than patching vendor code.
Test the full workflow with Livewire/Filament tests: create a form, render it, submit valid and invalid payloads, assert validation errors, and assert database rows.
For deployment, pin the package version, run migrations, publish required assets, and clear/rebuild caches.

The v0.1 release notes do not describe runtime changes. Do not infer stability or new functionality from this release; review the README and source before adopting.
Pin the exact version in composer.json while the package is early. Expect possible API, config, or schema changes in later releases.
Confirm the Filament plugin class name and namespace from the package docs before registering it. Do not copy plugin registration snippets from unrelated Filament packages.
Check whether publish tags actually exist. If a documented tag fails, run php artisan vendor:publish without a tag and inspect the list.
Dynamic validation and file uploads are common failure points. Verify validation rule serialization, storage disk configuration, file cleanup, and authorization on uploaded files.
If the package supports multi-tenancy, verify its scoping behavior. If not, add tenant scoping in your own queries and policies.
Debug with composer show afsakar/filament-form-maker, php artisan about, php artisan migrate:status, and php artisan optimize:clear. Check Laravel logs for form rendering or submission errors.
Since there is no prior assessment, establish your own upgrade checklist: read changelog, run tests, verify migrations, and smoke-test form creation and submission before updating.