| Conditions | 3 |
| Paths | 1 |
| Total Lines | 64 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 0 | ||
Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.
For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.
Commonly applied refactorings include:
If many parameters/temporary variables are present:
| 1 | <?php |
||
| 21 | public function subscribe(ConnectionInterface $connection, stdClass $payload) |
||
| 22 | { |
||
| 23 | $this->verifySignature($connection, $payload); |
||
| 24 | |||
| 25 | $this->saveConnection($connection); |
||
| 26 | |||
| 27 | $this->channelManager->userJoinedPresenceChannel( |
||
|
|
|||
| 28 | $connection, |
||
| 29 | $user = json_decode($payload->channel_data), |
||
| 30 | $this->getName(), |
||
| 31 | $payload |
||
| 32 | ); |
||
| 33 | |||
| 34 | $this->channelManager |
||
| 35 | ->getChannelMembers($connection->app->id, $this->getName()) |
||
| 36 | ->then(function ($users) use ($connection) { |
||
| 37 | $hash = []; |
||
| 38 | |||
| 39 | foreach ($users as $socketId => $user) { |
||
| 40 | $hash[$user->user_id] = $user->user_info ?? []; |
||
| 41 | } |
||
| 42 | |||
| 43 | $connection->send(json_encode([ |
||
| 44 | 'event' => 'pusher_internal:subscription_succeeded', |
||
| 45 | 'channel' => $this->getName(), |
||
| 46 | 'data' => json_encode([ |
||
| 47 | 'presence' => [ |
||
| 48 | 'ids' => collect($users)->map(function ($user) { |
||
| 49 | return (string) $user->user_id; |
||
| 50 | })->values(), |
||
| 51 | 'hash' => $hash, |
||
| 52 | 'count' => count($users), |
||
| 53 | ], |
||
| 54 | ]), |
||
| 55 | ])); |
||
| 56 | }); |
||
| 57 | |||
| 58 | // The `pusher_internal:member_added` event is triggered when a user joins a channel. |
||
| 59 | // It's quite possible that a user can have multiple connections to the same channel |
||
| 60 | // (for example by having multiple browser tabs open) |
||
| 61 | // and in this case the events will only be triggered when the first tab is opened. |
||
| 62 | $this->channelManager |
||
| 63 | ->getMemberSockets($user->user_id, $connection->app->id, $this->getName()) |
||
| 64 | ->then(function ($sockets) use ($payload, $connection) { |
||
| 65 | if (count($sockets) === 1) { |
||
| 66 | $memberAddedPayload = [ |
||
| 67 | 'event' => 'pusher_internal:member_added', |
||
| 68 | 'channel' => $this->getName(), |
||
| 69 | 'data' => $payload->channel_data, |
||
| 70 | ]; |
||
| 71 | |||
| 72 | $this->broadcastToEveryoneExcept( |
||
| 73 | (object) $memberAddedPayload, $connection->socketId, |
||
| 74 | $connection->app->id |
||
| 75 | ); |
||
| 76 | } |
||
| 77 | |||
| 78 | DashboardLogger::log($connection->app->id, DashboardLogger::TYPE_SUBSCRIBED, [ |
||
| 79 | 'socketId' => $connection->socketId, |
||
| 80 | 'channel' => $this->getName(), |
||
| 81 | 'duplicate-connection' => count($sockets) > 1, |
||
| 82 | ]); |
||
| 83 | }); |
||
| 84 | } |
||
| 85 | |||
| 134 |
In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:
Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: