helpers.php ➔ json_widget() - Code Metrics - Inspection of "- reformat" - imanghafoori1/laravel-widgetize - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Push — master ( 1c625d...234c6d )

by Iman

created 2017-07-03 03:26 UTC

helpers.php ➔ json_widget() A

↳ Parent: Project

Complexity

Conditions	1
Paths	1

Size

Total Lines	4
Code Lines	2

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
cc	1
eloc	2
nc	1
nop	2
dl	0
loc	4
rs	10
c	0
b	0
f	0



<?php

if (!function_exists('render_widget')) {
    function render_widget($widget, ...$args)
    {
        return app(\Imanghafoori\Widgets\Utils\WidgetRenderer::class)->renderWidget($widget, ...$args);
    }
}

if (!function_exists('expire_widgets')) {
    function expire_widgets($tags)

    {
        return app(\Imanghafoori\Widgets\Utils\Cache::class)->expireTaggedWidgets($tags);
    }
}

if (!function_exists('json_widget')) {
    function json_widget($widget, ...$args)

    {
        return app(\Imanghafoori\Widgets\Utils\WidgetJsonifier::class)->jsonResponse($widget, ...$args);
    }
}


1
			0 ignored issues – show Security Bug introduced 2017-05-30 18:04 UTC by Report Bug Copy Issue Report It is not recommended to output anything before PHP's opening tag in non-template files. Loading history... Coding Style Compatibility introduced 2017-05-30 18:04 UTC by Report Bug Copy Issue Report For compatibility and reusability of your code, PSR1 recommends that a file should introduce either new symbols (like classes, functions, etc.) or have side-effects (like outputting something, or including other files), but not both at the same time. The first symbol is defined on line 5 and the first side effect is on line 1. The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file. The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place. To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1. Loading history...
2			<?php
3
4			if (!function_exists('render_widget')) {
5			function render_widget($widget, ...$args)
6			{
7			return app(\Imanghafoori\Widgets\Utils\WidgetRenderer::class)->renderWidget($widget, ...$args);
8			}
9			}
10
11			if (!function_exists('expire_widgets')) {
12			function expire_widgets($tags)
			1 ignored issue – show Best Practice introduced 2017-05-30 18:04 UTC by Report Bug Copy Issue Report 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...
13			{
14			return app(\Imanghafoori\Widgets\Utils\Cache::class)->expireTaggedWidgets($tags);
15			}
16			}
17
18			if (!function_exists('json_widget')) {
19			function json_widget($widget, ...$args)
			1 ignored issue – show Best Practice introduced 2017-07-03 03:28 UTC by Report Bug Copy Issue Report 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...
20			{
21			return app(\Imanghafoori\Widgets\Utils\WidgetJsonifier::class)->jsonResponse($widget, ...$args);
22			}
23			}
24

imanghafoori1 / laravel-widgetize

Push — master ( 1c625d...234c6d )

helpers.php ➔ json_widget() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like