BaseNotification
last analyzed

Complexity

Total Complexity 0

Size/Duplication

Total Lines 17
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 0

Importance

Changes 0
Metric Value
wmc 0
lcom 0
cbo 0
dl 0
loc 17
c 0
b 0
f 0

4 Methods

Rating   Name   Duplication   Size   Complexity  
getNotifiable() 0 1 ?
getChannels() 0 1 ?
getNotificationArray() 0 1 ?
setNotifiable() 0 1 ?
1
<?php
2
3
namespace IrishDan\NotificationBundle\Notification;
4
5
abstract class BaseNotification implements NotificationInterface
6
{
7
    // @TODO: Currently in the interface
8
    abstract function getNotifiable();
0 ignored issues
show
Best Practice introduced by
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...
9
10
    abstract public function getChannels();
11
12
    abstract public function getNotificationArray();
13
14
    abstract public function setNotifiable(NotifiableInterface $notifiable);
15
16
    // abstract public function toArray(NotifiableInterface $notifiable);
0 ignored issues
show
Unused Code Comprehensibility introduced by
50% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
17
//
18
    // abstract public function via(NotifiableInterface $notifiable);
0 ignored issues
show
Unused Code Comprehensibility introduced by
50% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
19
//
20
    // abstract public function toMail(NotifiableInterface $user);
0 ignored issues
show
Unused Code Comprehensibility introduced by
50% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
21
}