In Filament tables, you may want to show a relationship value with a conditional query. How do you use the Laravel subquery mechanism in Filament?
The problem with shouldRegisterNavigation() is that hiding the menu item doesn't protect you from someone accessing that URL by typing it manually in the browser. Security issue!
shouldRegisterNavigation()
Sometimes, just a text is not enough for a hint. That's where Filament allows you to render any Blade component or link inside of them.
Some resources might have too much information to display. In that case - we can use Tabs to filter them out for our users. Also, did you know you can have count badges on tabs?
If you have a "live" form with dynamic data, it's beneficial to show the "loading" icon to users, so they would understand what's happening on the screen.
If you need to test project(s) locally and don't want to enter login/password every time, you can use a plugin by Spatie and hook it into Filament.
Default Filament design comes without any footer. But you can easily add it.
If you have a longer registration form, you may want to split it into steps, with wizard, including different validation rules.
When dealing with invoices or orders - we usually have a Quantity field next to a Product field. To provide a better user experience, we should clear a related field once the parent value changes. We don't want to see our users order too much of a different thing, do we?
Your form might have related fields set, like countries and cities. This is great, but it poses an issue—without resetting the related fields, selecting a city that doesn't belong to the country becomes possible. This can cause some errors, so let's fix it!
