filamentphp/filament v3.0.0-beta1

on GitHub

If you're interested in testing v3 beta, thank you so much for taking part! You will be helping us by ensuring that v3 is stable enough for public use and release on the 1st of August.

You can find the beta docs at https://beta.filamentphp.com. The upgrade guide for the admin panel from v2, can be found on there. To install it, you'll need to use "minimum-stability": "dev" in your composer.json file - newer installations of Laravel use stable.

It's come to our attention that Composer is installing alpha versions of v3 instead of beta, leading to weird experiences. You can check with php artisan about. If that's the case, in composer.json use ^3.0@beta as the version constraint and it should be fixed.

However, it's best that we set some of your expectations, to ensure that you have a good experience, especially when interacting with project maintainers.

1. This is a very busy period for core maintainers of Filament. There are 5 people on the team, and we have full time jobs alongside Filament. Please be nice.
2. Things might take a little longer to process than you want or expect.
3. Support, especially on GitHub and Discord, will be much slower, or non-existent.
4. The experience using the Filament v3 beta may be substandard, buggy, or missing features.
5. The documentation may be wrong, or missing vital information.
6. The upgrade experience from v2 may be slow and painful. Especially if you have heavy customization.
7. If you're not reporting things in GitHub issues, they will likely get lost. Especially if you attempt to report bugs on Discord or in direct messages with maintainers. Those bugs are not tracked and will not be fixed.
8. This applies to all GitHub issues, but if you make no effort to provide a reproduction repository for an issue, it will be closed and not investigated. Please reproduce issues in a new project, and not your existing project. We are not interested in code that is not directly required to replicate the problem.
9. It's very likely that third party plugins will not be compatible with v3 yet. Be nice to plugin authors as well!
10. We expect you to submit pull requests for typos, especially to the documentation. Please do not open issues for these, the core team needs to focus on issues with the actual codebase.

If any of these things disappoint you, please do not use Filament v3 beta!

Now that we've set some expectations, I'd like to outline the priorities of Filament team members during the beta period:

1. Supporting v2 plugin authors to upgrade to v3. If you are a v2 plugin author and require support, please contact the core team in the #plugin-developers-chat channel on our Discord server. You will need to resubmit your plugins to our website as there are new quality guidelines to follow - the process is documented here. All PRs should be made to the new-design branch on the filamentphp.com repo.
2. Fixing critical bugs, especially those that did not exist in the same functionality of v2. Bugs in new v3 features will likely not be a priority to fix.
3. Improving the upgrade experience by adding rules to the automated upgrade script.

We are not prioritising adding new features to v3 at this time. If you submit a PR or make a feature request, it's quite likely that it will not be merged for weeks, especially if it is large.

Again, thank you for helping us out and respecting our time. We hope that you enjoy trying out all the new stuff we have in store, and love the new design!