Closed jaydorsey closed 5 years ago
Thanks for the feedback. We’re sorry that you’ve spent that much time debugging the issue. The check is implemented in Pusher server, not on the library side. We will make sure to update the documentation to mention this!
Would the problem have been clearer with a better error message? i.e.:
Pusher::Error (Bad request: Event names cannot be prefixed with 'pusher')
I do think that message is clear.
With the namespace
nomenclature in the error we were looking at things like gem version, an API change, deprecated syntax, etc.
That makes sense. Thanks for the feedback!
We will fix this by updating the error message. I'll close this issue since this is a change that will be made to the Channels API; not this library.
Good afternoon, I ran into this error today:
We had a snippet of code that looked like this:
Swapping out
pusher-notification
fornew-notification
resolved the issue, but I didn't see this namespace reserved either in this library, or in the API docs. It took me far longer to debug than I would have liked, so if it is part of the API rules it might be nice to add a check on the library side to prevent this kind of event naming.I'm using the latest published gem (1.3.2)