Skip to content

[Turbo] Moving repeatable Broadcast changelog to 2.3 #388

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 8, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion src/Turbo/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,12 @@
# CHANGELOG

## 2.3

- The `Broadcast` attribute can now be repeated, this is convenient to render several Turbo Streams Twig templates for the same change

## 2.2

- The topics defined in the `Broadcast` attribute now support expression language when prefixed with `@=`.
- The `Broadcast` attribute can now be repeated, this is convenient to render several Turbo Streams Twig templates for the same change

## 2.1

Expand Down
8 changes: 4 additions & 4 deletions src/Turbo/Resources/doc/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -620,10 +620,10 @@ The ``Broadcast`` attribute comes with a set of handy options:
is derived from the FQCN of the entity and from its id
- ``template`` (``string``): Twig template to render (see above)

The ``Broadcast`` attribute can be repeated. This is convenient to
to render several templates associated with their own topics for the
same change (e.g. the same data is rendered in different way in the
list and in the detail pages).
The ``Broadcast`` attribute can be repeated (e.g. you can have multiple
`#[Broadcast]`. This is convenient to to render several templates associated with
their own topics for the same change (e.g. the same data is rendered in different
way in the list and in the detail pages).

Options are transport-specific. When using Mercure, some extra options
are supported:
Expand Down