1.3.0 - 1.3.2 - Breaking changes

[catalinux]

I think that this changes 7b7dd5f?diff=split added breacking changes.

In 1.3.0 we had following

PHP:

public function broadcastAs()
    {
        return 'alerts\created';
    }

JS:

channel.listen('.alerts.created', (event) => {})

Everything worked great, because EventFormatter would return alerts\created

Now in 1.3.2

when I do channel.listen('.alerts.created', (event) => {}) it will look for alerts.created (that is what EventFormmatter` returns)

Is there a way we could prevent other users to spent hours in debugging. Minor versions should not add breaking changes

[mbarwick83]

Any update on this? Notifications are no longer working for me, running 1.3.2

[catalinux]

You have to adapt your event names from php app

[mbarwick83]

Thanks. But do you care to elaborate? I'm using echo's notification method.

[ellisio]

Please refer to PR #140 for why the way you were implementing was actually the broken way. The PR was merged to align the code with the documentation.

[robclancy]

Lack of a changelog for this makes it risky to update anything.

[ellisio]

If you followed the Laravel documentation, then you are fine and the risk is minimal.