1.3.0 - 1.3.2 - Breaking changes
See original GitHub issueI think that this changes https://github.com/laravel/echo/commit/7b7dd5f1bd0b6bf60140ce6d2594b3fd0357eb7c?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
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Upgrading to v1.3 (latest) - dbt Developer Hub
Breaking changes . We are committed to providing ... There are three changes in dbt Core v1.3 that may require action from some...
Read more >fastcore/CHANGELOG.md at master - Release notes - GitHub
1.0.1. Breaking Changes. Change arguments of store_attr() and remove store_attrs attribute (#71). store_attr 's API has ...
Read more >Upgrading to Vault 1.3.2 - Guides - HashiCorp Developer
This page contains the list of deprecations and important or breaking changes for Vault 1.3.0 compared to 1.3.2. Please read it carefully.
Read more >Changelog | Meteor API Docs
meteor-developer-oauth@1.3.2 ... service-configuration@1.3.0 ... This could be a breaking change for 1.3.2 apps that do not use modules or ecmascript but ...
Read more >What's new in 1.3.0 (July 2, 2021) - Pandas
These are bug fixes that might have notable behavior changes. Categorical.unique now always maintains same dtype as original#. Previously, when calling ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If you followed the Laravel documentation, then you are fine and the risk is minimal.
Lack of a changelog for this makes it risky to update anything.