Best practise for features that an app should have

@Snapey

1. Test: Yes, I am working on them and keep track of the coverage
2. I am using filament, so my front end is built with Livewire components using the filament tables/forms, so I think the validation is covered.
3. I've implemented rmsramos/activitylog which is a Filament plugin built upon Spatie/Laravel-activitylog. It allows the admins to view all actions taken upon a given model, what is the action and who has executed the action. Also, in case of an update, it also shows which fields are updated with their old and new value. Is that the kind of logs you are talking about?

P.S.: I am using Filament to create a dedicated panel for Administrators/Moderators, and I do not have a dedicated panel for the front end as my theme is quite custom and not very suited for implementation alongside a filament panel.

@Merklin Ref 3. No, I meant error logs.

@Merklin 2. You still need to set validation up in the form() for each field.

@Sinnbeck You mean like setting string(), email(), required etc.? Yes, I have that. The only thing I have not tuned yet is to set the allowed length for strings. Anyway, my forms, tables, infolists etc. are refactored into a trait for each model and I used the trait whenever and wherever needed so this will be no issue as a final touch.

@Merklin Ok great. That was indeed what I meant

@martinbean True, but @Snapey's proposal to add the ability to look at the error log within the application was spot-on. I found this package.

Also, it is not said that I will add/implement everything that is proposed. You can learn something every day even in a casual talk.

True, but @Snapey's proposal to add the ability to look at the error log within the application was spot-on. I found this package.

@Merklin I use things like Sentry for viewing errors logs; not routes in my own application.