Zep Fietje
When you dive deep into accessibility specs, you realize not a single component library gets it right... E.g. focusing the first menu item only ever happens when menu is triggered by keyboard, not on button click. Makes me wonder if that’s by design (for example in @base-ui.com).
So have you signed up for early access of the custom Filament theme designer yet? You might want get on the list now. That’s all I’m saying. 🤫 filamentthemes.com/themes/custom
Have you seen the new factory “insert” method introduced in last week’s Laravel release? Just used it to refactor store creation for the Filament Themes demo — so much cleaner. 🤤 Thanks @cosmastech.bsky.social! 🫶
Even better for simple single-line getters... 👇
Using PHP property hooks a lot lately. Absolutely love this “memoized computed property” pattern. It ensures computationally heavy class properties are calculated only once, even when accessed multiple times. So much cleaner than a separate method and property. 🤤
Fun fact: Laravel’s latest products, Nightwatch and Cloud, also follow the single-password-field pattern at sign-up! 😄 Laravel Cloud even leaves out the name field. Makes me wonder if that would be an even better approach...
Unpopular opinion: “Confirm password” fields are bad. Forcing users to enter passwords twice adds friction and lowers conversion rates. Why optimize for a couple users who make a typo? Just let them reset their password. More friction for a few, less friction for most. 👌