[Turbo] Minor documentation syntax fixes

[seb-jean]

Q	A
Bug fix?	no
New feature?	no
Docs?	yes
Issues	Fix #...
License	MIT

Fixed documentation regarding blocks when using broadcast. Blocks are not required.

[smnandre]

When did this change ?

[seb-jean]

I don't know when it changed but I only tested with the create block in my template and I didn't encounter any errors.

[smnandre]

Even during an update and a remove broadcast (just to be sure) ?

[seb-jean]

Exactly, it also works for update and remove.

[seb-jean]

And of course, they are mandatory when creating, deleting or updating, otherwise an error is returned.

[smnandre]

Wait so they "can" or they "must" ?

[seb-jean]

create block must be present if it's a creation.
update block must be present if it's an update.
remove block must be present if it's a deletion.

For example, for my Book entity, I need to render a template on creation and update. I should have the following code:

{# templates/broadcast/Book.stream.html.twig #}
{% block create %}
  [...]
{% endblock %}

{% block update %}
  [...]
{% endblock %}

The remove block isn't present, and it works.

With the current documentation, the developer will think it's necessary to do this:

{# templates/broadcast/Book.stream.html.twig #}
{% block create %}
  [...]
{% endblock %}

{% block update %}
  [...]
{% endblock %}

{% block remove %}
{% endblock %}

With an empty remove block, but this isn't necessary.

[smnandre]

I'm not sure i agree with this way of presenting thing. Their entity can be deleted or updated. If this happens and they did not put these blocks here, their app will crash.

I'd say we need either a way to explain it very clearly, or let's keep the current formulation.

WDYT ?

[seb-jean]

Yeah ok, let's keep the current formulation then :).

[Kocal]

Thank you @seb-jean.