Stormlight

@Toby I'm currently using Livewire alongside Waterhole but after reading this, I am considering switching to Hotwire.

I started my project off with the Waterhole Skeleton Repo (composer create-project waterhole/waterhole), and I was considering installing Turbo-Laravel as a package rather than relying on the version Waterhole/core is using (so I could update to the latest version of Turbo-Laravel faster than relying on Waterhole updating it's dependencies).

My question is, do you think that's a wise idea? My concern is that having two versions of Hotwire could cause issues.

But you are free (not in the monetary sense) to modify and redistribute Waterhole, you just have to abide by what's stated in the licence.

So, in the case of redistribution, you're free to do that, provided that you pay Waterhole for every licence that you give out.

Section 6 of the Waterhole licence
(e) a Licensee or Authorised User making the Software available to third parties via a Software-as-a-Service (SaaS) offering, provided that a separate Production Licence is purchased for each separate project or separate client.

I think it's a common misconception that open source equals free (monetary), it does not, though it can be free of cost.

The code is available for everyone to see on GitHub, so that makes it open source.

I think I figured out the issue, waterhole/core requires a beta version of turbo-laravel:

waterhole/core v0.4.8 requires hotwired-laravel/turbo-laravel ^2.0.0-beta5 -> found hotwired-laravel/turbo-laravel[2.0.0-beta5, 2.x-dev] but it does not match your minimum-stability.

Also, the Waterhole Starter Skeleton project has the following in the composer.json:

    "minimum-stability": "stable",
    "prefer-stable": true

Is there any risk of switching minimum stability to beta? That was the only way I was able to update the Waterhole Starter Skeleton project.

Hey Toby, I'm assuming 0.4.8 is yet to be released? As composer update doesn't pull in that version nor does starting a new project via composer create-project waterhole/waterhole path/to/forum.

Also, regarding conditional rendering, the use of a closure doesn't seem to work with the Extend remove method as it only accepts a string param. Is this method going to be updated in the future to allow for mixed content instead of only strings? I was trying to conditionally remove some of the buttons in the text editor but it seems they are hard coded, so using the replace method wasn't viable (source code).