I’m using it to show localized pricing based on the visitor’s country and available price currencies retrieved directly from Stripe.
Thanks, Symfony team! (And congrats on the 8.0 release! 🥳)
I’m using it to show localized pricing based on the visitor’s country and available price currencies retrieved directly from Stripe.
Thanks, Symfony team! (And congrats on the 8.0 release! 🥳)
Anyone else upgraded yet?
Anyone else upgraded yet?
So happy with everyone’s positive responses ☺️
Keep an eye on your inbox if you’re on the list!
So happy with everyone’s positive responses ☺️
Keep an eye on your inbox if you’re on the list!
Can't wait to start using the pipe operator and array_first/array_last functions... 😄
Can't wait to start using the pipe operator and array_first/array_last functions... 😄
Nice one! 😂
Nice one! 😂
Just used it to refactor store creation for the Filament Themes demo — so much cleaner. 🤤
Thanks @cosmastech.bsky.social! 🫶
Just used it to refactor store creation for the Filament Themes demo — so much cleaner. 🤤
Thanks @cosmastech.bsky.social! 🫶
Thanks for listening to the complaints, Apple. 🍎
Thanks for listening to the complaints, Apple. 🍎
Don’t ask me why 😂
Don’t ask me why 😂
1. Store hooks in .hooks to version them with Git.
2. Add "git config core.hooksPath .hooks" to your Composer setup script to link the hooks during setup after cloning the repo.
Super easy, zero dependencies.
1. Store hooks in .hooks to version them with Git.
2. Add "git config core.hooksPath .hooks" to your Composer setup script to link the hooks during setup after cloning the repo.
Super easy, zero dependencies.
Has anyone tried relying only on native hooks instead of Eloquent’s feature?
Any limitations you’ve hit?
Has anyone tried relying only on native hooks instead of Eloquent’s feature?
Any limitations you’ve hit?
Inline feedback is often enough: clear, unobtrusive, and right where the user is focused. 👇
Inline feedback is often enough: clear, unobtrusive, and right where the user is focused. 👇
Then, all you need in your Blade view is:
x-data="tabs"
Then, all you need in your Blade view is:
x-data="tabs"
Blade, CSS, and JS, all grouped in a single component folder.
Can’t imagine doing it any other way now…
Blade, CSS, and JS, all grouped in a single component folder.
Can’t imagine doing it any other way now…
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. 🤤
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. 🤤
Just like it does for resources, pages, and widgets. Perfect for keeping panel-specific components organized, scoped to the panel, and alongside your main folders. 👌
Just like it does for resources, pages, and widgets. Perfect for keeping panel-specific components organized, scoped to the panel, and alongside your main folders. 👌
Just press command + space and then command + 4.
Really digging the Spotlight improvements in macOS Tahoe in general! 👍
Just press command + space and then command + 4.
Really digging the Spotlight improvements in macOS Tahoe in general! 👍
The absolute truth, Nielsen Norman Group, tells you to not repeat password fields! 🤣
The absolute truth, Nielsen Norman Group, tells you to not repeat password fields! 🤣
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...
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...
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. 👌
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. 👌