{"action":"created","issue":{"url":"https://api.github.com/repos/laravel/internals/issues/202","repository_url":"https://api.github.com/repos/laravel/internals","labels_url":"https://api.github.com/repos/laravel/internals/issues/202/labels{/name}","comments_url":"https://api.github.com/repos/laravel/internals/issues/202/comments","events_url":"https://api.github.com/repos/laravel/internals/issues/202/events","html_url":"https://github.com/laravel/internals/issues/202","id":176267534,"number":202,"title":"[Proposal] Ability to define Notifications broadcast channel name","user":{"login":"mikemclin","id":1570155,"avatar_url":"https://avatars.githubusercontent.com/u/1570155?v=3","gravatar_id":"","url":"https://api.github.com/users/mikemclin","html_url":"https://github.com/mikemclin","followers_url":"https://api.github.com/users/mikemclin/followers","following_url":"https://api.github.com/users/mikemclin/following{/other_user}","gists_url":"https://api.github.com/users/mikemclin/gists{/gist_id}","starred_url":"https://api.github.com/users/mikemclin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mikemclin/subscriptions","organizations_url":"https://api.github.com/users/mikemclin/orgs","repos_url":"https://api.github.com/users/mikemclin/repos","events_url":"https://api.github.com/users/mikemclin/events{/privacy}","received_events_url":"https://api.github.com/users/mikemclin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-09-11T21:52:20Z","updated_at":"2016-09-13T01:22:20Z","closed_at":null,"body":"Currently the Notifications broadcast channel broadcasts to a dot-separated, capitalized version of the notifiable's namespace (e.g. `App.User`).  However all of the example channel names in the docs seem to follow a lowercased basename format (e.g. `user`).\r\n\r\nObviously most people will want a consistent naming strategy for their channel names.  Personally, I prefer the convention in the docs, because my client app doesn't need to know about my model paths in my API.\r\n\r\nAnyways, it would be great if there was a hook of some sort, so we could set the channel name for a notification.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/laravel/internals/issues/comments/246545451","html_url":"https://github.com/laravel/internals/issues/202#issuecomment-246545451","issue_url":"https://api.github.com/repos/laravel/internals/issues/202","id":246545451,"user":{"login":"fgambino","id":1589195,"avatar_url":"https://avatars.githubusercontent.com/u/1589195?v=3","gravatar_id":"","url":"https://api.github.com/users/fgambino","html_url":"https://github.com/fgambino","followers_url":"https://api.github.com/users/fgambino/followers","following_url":"https://api.github.com/users/fgambino/following{/other_user}","gists_url":"https://api.github.com/users/fgambino/gists{/gist_id}","starred_url":"https://api.github.com/users/fgambino/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fgambino/subscriptions","organizations_url":"https://api.github.com/users/fgambino/orgs","repos_url":"https://api.github.com/users/fgambino/repos","events_url":"https://api.github.com/users/fgambino/events{/privacy}","received_events_url":"https://api.github.com/users/fgambino/received_events","type":"User","site_admin":false},"created_at":"2016-09-13T01:22:20Z","updated_at":"2016-09-13T01:22:20Z","body":"@mikemclin no apology necessary. I can definitely see the confusion there. We can continue discussion in this issue!\r\n\r\nWhat if a `routeNotificationForBroadcast()` method was added to the notifiable model/user? That would keep things consistent with how other routes are customized (email, slack, etc). "}}
{"actor":{"display_login":"fgambino"}}