Passed
Pull Request — master (#78)
by
unknown
06:02
created

HtmlOutput   A

Complexity

Total Complexity 7

Size/Duplication

Total Lines 56
Duplicated Lines 0 %

Importance

Changes 1
Bugs 0 Features 0
Metric Value
wmc 7
eloc 8
c 1
b 0
f 0
dl 0
loc 56
rs 10

7 Methods

Rating   Name   Duplication   Size   Complexity  
A getNewlineElementTemplate() 0 3 1
A getPaymentPartTemplate() 0 3 1
A getPrintableStylesTemplate() 0 3 1
A getTitleElementReceiptTemplate() 0 3 1
A getPlaceholderElementTemplate() 0 3 1
A getTitleElementTemplate() 0 3 1
A getTextElementTemplate() 0 3 1
1
<?php
2
3
namespace Sprain\SwissQrBill\PaymentPart\Output\MarkupOutput;
4
5
use Sprain\SwissQrBill\PaymentPart\Output\MarkupOutput\Template\Html\NewlineElementTemplate;
6
use Sprain\SwissQrBill\PaymentPart\Output\MarkupOutput\Template\Html\PlaceholderElementTemplate;
7
use Sprain\SwissQrBill\PaymentPart\Output\MarkupOutput\Template\Html\PrintableStylesTemplate;
8
use Sprain\SwissQrBill\PaymentPart\Output\MarkupOutput\Template\Html\TextElementTemplate;
9
use Sprain\SwissQrBill\PaymentPart\Output\MarkupOutput\Template\Html\PaymentPartTemplate;
10
use Sprain\SwissQrBill\PaymentPart\Output\MarkupOutput\Template\Html\TitleElementReceiptTemplate;
11
use Sprain\SwissQrBill\PaymentPart\Output\MarkupOutput\Template\Html\TitleElementTemplate;
12
13
final class HtmlOutput extends AbstractMarkupOutput
14
{
15
    /**
16
     * @return string
17
     */
18
    function getPaymentPartTemplate(): string
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...
19
    {
20
        return PaymentPartTemplate::TEMPLATE;
21
    }
22
23
    /**
24
     * @return string
25
     */
26
    function getPlaceholderElementTemplate(): string
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...
27
    {
28
        return PlaceholderElementTemplate::TEMPLATE;
29
    }
30
31
    /**
32
     * @return string
33
     */
34
    function getPrintableStylesTemplate(): string
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...
35
    {
36
        return PrintableStylesTemplate::TEMPLATE;
37
    }
38
39
    /**
40
     * @return string
41
     */
42
    function getTextElementTemplate(): string
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...
43
    {
44
        return TextElementTemplate::TEMPLATE;
45
    }
46
47
    /**
48
     * @return string
49
     */
50
    function getTitleElementTemplate(): string
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...
51
    {
52
        return TitleElementTemplate::TEMPLATE;
53
    }
54
55
    /**
56
     * @return string
57
     */
58
    function getTitleElementReceiptTemplate(): string
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...
59
    {
60
        return TitleElementReceiptTemplate::TEMPLATE;
61
    }
62
63
    /**
64
     * @return string
65
     */
66
    function getNewlineElementTemplate(): string
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...
67
    {
68
        return NewlineElementTemplate::TEMPLATE;
69
    }
70
}
71