Flux uses Tiptap for its Editor component - offering incredible interoperability with Statamic's Bard fieldtype. With one catch: Flux's implementation returns HTML.
Never fear, @joshhanley.au paired with me to help tweak the getter to get JSON instead.
www.martyfriedel.com/blog/making-...
Livewire v4 beta has been tagged! Go forth ⚡️ github.com/livewire/liv...
Docs can be found here livewire.laravel.com/docs/4.x/upg...
Agreed!
You might be waiting a while, it’s not something we plan to change. What’s wrong with tables?
Yep! All in the matter of time 😁
We've just fixed up how sidebar groups are handled, so make sure to upgrade to v2.3.1!
We just shipped a ton of improvements to Flux's sidebar! 👌
- Collapsible sidebars
- Collapsed state auto-persisted in localStorage
- Sidebar item group icons
- New `sidebar.search` component
- + like 5 other new sidebar components
Checkout the blog post: fluxui.dev/blog
Love it! 😁 yep it’s a default for all projects for me now 😊
New Flux release: v2.2.4 with a bunch more fixes! 😁
And how are you going?
Yep, a good friend will always want to know. There have been times when I've got so much going on in my world, when I call my best friend, I rant for a bit. But then I always ask, so how're you doing? No matter how long into the conversation we may be. But it goes both ways.
Soon ™️
To all of those social butterflies in Denver - enjoy Laracon!
Don’t forget to keep an eye out for someone seeming on the outer, someone needing to feel included, someone needing a smile.
There are lots of invisible developers out there.
Try to do something that can help others feel seen.
Here's another great article that changed how I viewed storing dates/times www.creativedeletion.com/2015/03/19/p...
Thankfully, while events aren't fun to deal with, they are definitely reliable. I've been using this pattern even since v2 for shared modals.
Yep! Just tested this and yeah it works as I was hoping 😁
I think I know what you want and it's coming in v4 🤫👀 (if it works the way I'm hoping it will 😆)
Yeah the main reason for the dispatch is, what if you click edit on one user, then escape out and then click edit on a different user? The modal comp can't mount twice. You could potentially do that if you had inline modals but that adds to the DOM. I just have one edit-user modal comp for the page.
I'd love to know the answer to this too 😅
I then have loading inside the modal, which `wire:target` the edit method, to show the loading state and hide the modal contents.
Yep, that's how I do it. I have a button that has `wire:click="$dispatch('edit-user', {{$user->id}})"` and it is wrapped in a `flux:modal.trigger` component, which opens the modal.
My modal component has a listener for the edit-user event on my `edit($userId)` method.
One component for the page and another for the modal 😁
Ahh! Yep, that'll do it. What do you use that for?
Actually those dates are off by a day in comparison to the date inside the element 🤔
Yeah Flux uses browser locale based date objects to get the individual dates. But it should only be rendering the day and not the rest of it.
Sadly not. If you can’t work it out, happy to jump on a call to see if we can get to the bottom of it.
Very strange! Just tested locally and I couldn’t get it to break 😅 thought maybe it was an issue with date picker after flux scripts or something. But it doesn’t function at all then 😂
Ok thanks. I’ll have a quick play and see if I can replicate it. Does seem odd styles wouldn’t be there initially but be fine after any interaction
Nope! I’ll test it out. Assuming it’s nothing fancy, just date picker inside a fly out modal?
Haha was just keeping them for a little while after I migrated to digital ocean. Probably should clean them up but yeah it’s not worth it 😂
Yeah same, mines like $1 for some old RDS snapshots 😂
