In reply to
Toby
Toby
Waterhole
Founder
Apr 11, 2024
Yep, that's right about conditional rendering - there's a note on this in the Extenders doc. The way you've done it works well, or an alternative would be to replace the search component with a closur...
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).
Unfortunately I don't think it's currently possible to add traits to the Waterhole User model. Again, I'll look into making the User model configurable so you can subclass it, but for now your options are to implement the desired relations manually using
resolveRelationUsing
, or use your own separate User model/table and then set up the Laravel authentication integration.Haven't tested, but try this: