Skip to content

Releases: hotwired-laravel/turbo-laravel

1.12.0

29 Mar 02:01
e5995e2
Compare
Choose a tag to compare

Changelog

  • FIXED: Fixes the redirect route guessing behavior when using form requests, since in that case, Laravel will set the exception's redirectTo, bypassing the guessing behavior. Thanks, @yttrian, for reporting it (see #105)
  • NEW: Adds a new redirect_guessing_exceptions config in the turbo-laravel.php for adding exceptions to the guessing behavior. The internal redirect will still happen when using this config, just not the route-guessing behavior.

1.11.1

07 Mar 18:57
300bacc
Compare
Choose a tag to compare

Changelog

  • FIXED: The TurboMiddleware was automatically registered to the "web" route group. But something must have changed in Laravel 10, and that was no longer working. The issue was fixed by prepending the middleware via the HTTP Kernel instead of via the Route facade. See #103

1.11.0

14 Feb 01:25
f175456
Compare
Choose a tag to compare

Changelog

  • CHANGED: Support for Laravel 10

1.10.0

01 Feb 12:19
37671cf
Compare
Choose a tag to compare

Changelog

  • CHANGED: Bumped Turbo.js to 7.2.5, Laravel Echo to 1.15.0, Pusher.js to 8.0.1, and Alpine.js to 3.11.1 in the turbo:install command (for new installs)

1.9.0

06 Jan 00:43
d068ee8
Compare
Choose a tag to compare

Changelog

  • NEW: Turbo Stream broadcasts are now decoupled from models! Testing broadcasts was also improved! (#97 and handmade broadcasts docs and testing broadcasts docs)
  • FIXED: The turbo-echo-stream-source custom HTML tag that ships with the package was not being able to connect to public channels (#98)

1.8.1

28 Dec 22:50
d3f5ad8
Compare
Choose a tag to compare

Changelog

  • FIXED: Ensure the published turbo-echo-stream-source custom HTML element is defined only once (d3f5ad8)

Note: Those that already have the custom element published may change the file manually.

1.8.0

10 Dec 00:25
eefef6f
Compare
Choose a tag to compare

Changelog

  • NEW: Turbo Stream Blade component now supports custom Turbo Stream actions #95

1.7.0

09 Dec 16:22
be18e37
Compare
Choose a tag to compare

Changelog

  • NEW: The PendingTurboStreamResponse is now macroable (#94)

1.6.0

18 Sep 18:34
a7c34ab
Compare
Choose a tag to compare

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:

1.5.1

03 Jul 00:12
c769ecb
Compare
Choose a tag to compare

Changelog

  • FIXED: Fixed the regex pattern to match the bootstrap JS import in the app.js