I’ve just published a Laravel Livewire chat package called Wirechat! 🎉
Wirechat is designed to make it super easy to add real-time chat to your Laravel apps, whether you need private 1-on-1 chats, group conversations, disappearing messages, or more.
📚 Check out the docs: wirechat.namuio.com/docs
🎥 Watch the intro video: youtu.be/qT0ds2qa8VI
I’m excited to share this with you all—let me know your thoughts! 😊
In case I'm not the only one who has hidden migrations haunting them...
I was playing with `pgvector` locally a bit ago, did some migrations, rolled them back, and being in another branch I knew the migrations weren't being deployed....or so I thought...
A quick `$ find ....` and I found it in the vendor files.
I wrote up more here: peter.coffee/hidden-laravel-migrations
...hopefully it helps someone else who stumbles across this...
❓I'm also curious if there are some docs on this I'm missing somewhere...
Hello LaraDevs,
This week-end I played with VSCode by trying to develop a pestphp plugin in laravel context.
For now, it's really just a baby and as every baby he needs some support from you, his name is Pestimony.
Look 👀 👇
So it's obviously not perfect but he already can help you with:
- generate feature test with user interaction for filename, name of the test and asking if the test has to have RefreshDatabase Trait
- generate unit test with user interaction for filename, name of the test
- run single test
- run a tests suite
- run all tests
- run test directly in the source code
- rerun failed tests only
- visualize easily the tests passed and tests failed
marketplace.visualstudio.com/items?itemName=happytodev.pestimony-vscode-plugin
note to self: never use livewire on client sites. Maybe for personal new sites is okay but don't throw it on legacy stuff. You will get white hairs
Because If it's a personal project I can afford to delay it but clients have deadlines to respect.
From my personal experience livewire is not stable enough yet for clients requiring stable experience and fat turn around. I'm almost sure the issue came from integrating legacy ad livewire but it because of this bad choice of mine I had to spend some mentally tiring 3 weeks and delay a second project which I was working in the meantime (50/50 time sure).
I repeat it was my fault for experimentating with new tech on clients projects.
Here i described my experience better alpha.coz.jp/X3mdRb
Hey fellow Laravel devs. I am building custom fields feature for my app and it has relationship to different models via polymorphic relations. when creating a new custom field, I provide model that this field belongs to so that I can attach it. The question is how should I implement updating and deleting these fields? Once created I can use the id of the custom field to update and delete it so is it okay to just pass the field id instead of passing model and field in the route?
By that moment, you should have something like this:
fields: id, fieldable_type, field_type, field_label, ...
custom_options: id, field_id, fieldable_id, fieldable_type.
And in your custom_options, the value will be something like:
1, 1, 1, App\Models\User
So if you have all required foreign key contraints with cascade delete, then removing the entry from `fields` table, the related `custom_options` will also be removed.
Hope I've answered your question or maybe I misunderstood it. In any case - feel free to ask, since I have made a similar solution 3 times already :D
