Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Laravel previously had some unexpected behavior (imo) when matching channels. This was raised to me via email by a community member.
If you have:
And you attempt to subscribe to channel
App.Interaction.some-uuid.Internal
, the channel will match; however, the injected parameter will just be "some-uuid"... ".Internal" will be removed. This is because the channel matching in Laravel was using a fairly naive Str::is check which did not match the regular expression logic of the parameter injection. IMO the logic should be the same between the two. So, I have updated the channel matching regular expression to match the parameter injection regular expression.In theory this could break applications that expected this route to match; however, those routes were already receiving a sliced parameter that may not be what they expect. So, I am viewing this as a bug. Will revisit if community feedback pushes back on release.
There was a test that showed this broken behavior but it appears to be added just out of thoroughness by a community member 4 years ago when the test was first added. Not for a specific use case.