Completed
Push — master ( 19af7f...765e83 )
by ARCANEDEV
14s queued 11s
created

helpers.php ➔ extract_date()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 4

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 1
nc 1
nop 1
dl 0
loc 4
rs 10
c 0
b 0
f 0
1
<?php
2
3
use Arcanedev\LogViewer\Contracts;
4
5
if ( ! function_exists('log_viewer')) {
6
    /**
7
     * Get the LogViewer instance.
8
     *
9
     * @return Arcanedev\LogViewer\Contracts\LogViewer
10
     */
11
    function log_viewer()
12
    {
13
        return app(Contracts\LogViewer::class);
14
    }
15
}
16
17
if ( ! function_exists('log_levels')) {
18
    /**
19
     * Get the LogLevels instance.
20
     *
21
     * @return Arcanedev\LogViewer\Contracts\Utilities\LogLevels
22
     */
23
    function log_levels()
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...
24
    {
25
        return app(Contracts\Utilities\LogLevels::class);
26
    }
27
}
28
29
if ( ! function_exists('log_menu')) {
30
    /**
31
     * Get the LogMenu instance.
32
     *
33
     * @return Arcanedev\LogViewer\Contracts\Utilities\LogMenu
34
     */
35
    function log_menu()
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...
36
    {
37
        return app(Contracts\Utilities\LogMenu::class);
38
    }
39
}
40
41
if ( ! function_exists('log_styler')) {
42
    /**
43
     * Get the LogStyler instance.
44
     *
45
     * @return Arcanedev\LogViewer\Contracts\Utilities\LogStyler
46
     */
47
    function log_styler()
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...
48
    {
49
        return app(Contracts\Utilities\LogStyler::class);
50
    }
51
}
52