It is generally recommended to explicitly declare the visibility for methods.
Adding explicit visibility (private, protected, or public) is generally
recommend to communicate to other developers how, and from where this method
is intended to be used.
Loading history...
28
{
29
echo 'Error: ';
30
echo $error."\n";
31
print_r($msg);
32
$data = [
33
'type'=>'error',
34
'message'=>$error
35
];
36
$this->sendToWebSocketUser($from,$data);
37
throw new WebSocketException();
38
}
39
40
/**
41
* @param ConnectionInterface $conn
42
* @param $data
43
*/
44
function sendToWebSocketUser(ConnectionInterface $conn,$data)
It is generally recommended to explicitly declare the visibility for methods.
Adding explicit visibility (private, protected, or public) is generally
recommend to communicate to other developers how, and from where this method
is intended to be used.
It is generally recommended to explicitly declare the visibility for methods.
Adding explicit visibility (private, protected, or public) is generally
recommend to communicate to other developers how, and from where this method
is intended to be used.
This check marks variable names that have not been written in camelCase.
In camelCase names are written without any punctuation, the start of each new word being marked
by a capital letter. Thus the name database connection string becomes databaseConnectionString.
It is generally recommended to explicitly declare the visibility for methods.
Adding explicit visibility (private, protected, or public) is generally
recommend to communicate to other developers how, and from where this method
is intended to be used.
Adding explicit visibility (
private,protected, orpublic) is generally recommend to communicate to other developers how, and from where this method is intended to be used.