1.6.0

Changelog

• NEW: The response macro now has return types which should help out autocompletion on some IDEs or when using the Laravel IDE Helper - by @nielsbauman (PRs #84 and #85)
• NEW: We now support targeting multiple elements on Turbo Streams by @timvdalen. See documentation (#86)
• NEW: On top of the multiple targets work mentioned above, we now have new appendAll(), prependAll(), updateAll(), replaceAll(), removeAll(), beforeAll, and afterAll methods that take a CSS class selector and the content (which can be a string, a View instance, or an instance of the HtmlSafe class) see the documentation - by @tonysm (#87)
• NEW: You may create turbo streams responses or tags now using the new turbo_stream() and turbo_stream_view() helper functions. These ship as namespaced functions under the Tonysm\TurboLaravel namespace, but also as globally available functions (easier to use them in contexts like Blade views, for instance). These work the same as the Response::turboStream() and Response::turboStreamView() macros (in fact, the macros now use them), they are just shorter. Suggested by @bilogic implemented by me @tonysm. See the documentation (#92)
• REMOVED: The --stimulus option was removed from the turbo:install command. It now only has the --jet for Jetstream installs and --alpine for Breeze installs. I'm working on a new package called Stimulus Laravel for the folks using Stimulus out there.

---

You may also have noticed that I am moving the documentation content to markdown files inside the docs/ folder. That's because I'm working on a new website where the docs will be hosted (and some more stuff I'm working on). So I'll keep the docs in the readme and inside the docs/ folder for now, but once it's ready, we'll only have them inside the docs/ folder.

Internal Breaking Changes

Some method signatures were changed to accommodate the new multiple targets behavior. We could have introduced the new targets attribute at the end method signature as nullable, but I've decided to change the order of the parameters, so the target and targets are closer to each other. Technically, this is a breaking change if you're extending BroadcastAction job class or manually creating these jobs. I didn't want to tag a major version because of this as I'm not aware of folks extending the internals of the package. If you do have an issue with that, please stick to the 1.5.x version and let me know.

This doesn't affect applications using the package normally, just those more advanced scenarios where folks are extending the internals here.

The signature changes were made to these classes:

• The Broadcaster interface and concrete implementation API changed
• The BroadcastAction job
• The PendingBroadcast class
• The TurboStreamBroadcast event