We wanted to reach out regarding the CBWire 4.x documentation, as we’ve recently attempted to upgrade from version 2.x to 4.x. Unfortunately, we had to roll back due to the lack of detailed documentation and clarity on the changes involved.
During our process, we found that the PHP Livewire documentation provided us with more insight than the CBWire resources, which left us a bit concerned. Could you please let us know when we can expect the CBWire documentation to be updated? Having comprehensive guidance would be incredibly helpful for our upgrade efforts.
Thank you for your attention to this matter. I look forward to your response.
@Jason_Daiger thanks for reaching out. You are right that the CBWIRE 4 documentation is in need of some much needed love and updating. I’m actively working on them and have pushed several documentation updates in the last week. You’ll see more doc updates coming in the next week or two, and a lot more on using AlpineJS with CBWIRE. I’ve been pushing a lot of patch updates on v4 and I think most of the major issues from the Livewire 3 overhaul have been resolved. In the meantime please feel free to reach out to me if you are running into any problems. Always happy to help! And again, sorry its taken so long on v4.
We’ve got v4 in production and it is working well. We worked with Grant on at least one patch. I can vouch for the effort he’s putting in on this. The lazy loading and overall performance improvements have really helped us out.
This is a nice chance to publicly thank Grant as well. He’s done an excellent job with CBWIRE. And he’s a joy to work with when issues come up. I always learn something when we’re on a call and he’s debugging my issue on my desktop. It is very efficient and he frequently gets to the bottom of my issue quite quickly.
As I update the documentation, I’ll make note of it here in this thread. If you have a moment, I’d greatly appreciate some extra sets of eyes and any feedback on where to improve the docs. Hang tight on giving feedback until I post another update here, as there are glaring issues with the v4 docs I’ll have resolved shortly.
