Cart - Code Metrics - Inspection of "Committing compiled files" - scottbedard/oc-shop-plugin - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Push — master ( 725f0a...f82868 )

by Scott

created 2016-11-28 15:46 UTC

Cart A

↳ Parent: Project

Complexity

Total Complexity

Size/Duplication

Total Lines	54
Duplicated Lines	0 %

Coupling/Cohesion

Components	0
Dependencies	1

Importance

Changes

Metric	Value
wmc	6
lcom	0
cbo	1
dl	0
loc	54
rs	10
c	0
b	0
f	0

3 Methods

Rating	Name	Size	Complexity
A	add()	10	2
A	show()	11	2
A	store()	11	2

<?php namespace Bedard\Shop\Api;

use Bedard\Shop\Classes\ApiController;
use Bedard\Shop\Repositories\CartRepository;
use Exception;
use Log;

class Cart extends ApiController
{
    /**
     * Add an inventory to the cart.
     *
     * @param CartRepository $repository
     */
    public function add(CartRepository $repository)
    {
        try {

            // @todo
        } catch (Exception $e) {
function fx() {
    try {
        doSomething();
        return true;
    }
    catch (\Exception $e) {
        return false;
    }

    return false;
}
            Log::error($e->getMessage());

            abort(500, $e->getMessage());
        }
    }

    /**
     * Show the current cart.
     *
     * @param  \Bedard\Shop\Repositories\CartRepository     $repository
     * @return \Bedard\Shop\Models\Cart
     */
    public function show(CartRepository $repository)
    {
        try {


            // @todo
        } catch (Exception $e) {
function fx() {
    try {
        doSomething();
        return true;
    }
    catch (\Exception $e) {
        return false;
    }

    return false;
}
            Log::error($e->getMessage());

            abort(500, $e->getMessage());
        }
    }

    /**
     * Create a new cart.
     *
     * @param  \Bedard\Shop\Repositories\CartRepository     $repository
     * @return \Bedard\Shop\Models\Cart
     */
    public function store(CartRepository $repository)
    {
        try {


            // @todo
        } catch (Exception $e) {
function fx() {
    try {
        doSomething();
        return true;
    }
    catch (\Exception $e) {
        return false;
    }

    return false;
}
            Log::error($e->getMessage());

            abort(500, $e->getMessage());
        }
    }
}


1			<?php namespace Bedard\Shop\Api;
2
3			use Bedard\Shop\Classes\ApiController;
4			use Bedard\Shop\Repositories\CartRepository;
5			use Exception;
6			use Log;
7
8			class Cart extends ApiController
9			{
10			/**
11			* Add an inventory to the cart.
12			*
13			* @param CartRepository $repository
14			*/
15			public function add(CartRepository $repository)
16			{
17			try {
			0 ignored issues – show Unused Code introduced 2016-11-28 15:48 UTC by Report Bug Copy Issue Report This `try` statement is empty and can be removed. This check looks for `try` blocks that have no statements or where all statements have been commented out. This may be the result of changes for debugging or the code may simply be obsolete. If there is nothing in the `try` then the `catch` block can never be executed either. Thus, these `try` statements can be removed completely. Loading history...
18			// @todo
19			} catch (Exception $e) {
			0 ignored issues – show Unused Code introduced 2016-11-28 15:48 UTC by Report Bug Copy Issue Report `catch (\Exception $e) { ...0, $e->getMessage()); }` does not seem to be reachable. This check looks for unreachable code. It uses sophisticated control flow analysis techniques to find statements which will never be executed. Unreachable code is most often the result of `return`, `die` or `exit` statements that have been added for debug purposes. function fx() { try { doSomething(); return true; } catch (\Exception $e) { return false; } return false; } In the above example, the last `return false` will never be executed, because a return statement has already been met in every possible execution path. Loading history...
20			Log::error($e->getMessage());
21
22			abort(500, $e->getMessage());
23			}
24			}
25
26			/**
27			* Show the current cart.
28			*
29			* @param \Bedard\Shop\Repositories\CartRepository $repository
30			* @return \Bedard\Shop\Models\Cart
31			*/
32			public function show(CartRepository $repository)
33			{
34			try {
			0 ignored issues – show Unused Code introduced 2016-11-28 15:48 UTC by Report Bug Copy Issue Report This `try` statement is empty and can be removed. This check looks for `try` blocks that have no statements or where all statements have been commented out. This may be the result of changes for debugging or the code may simply be obsolete. If there is nothing in the `try` then the `catch` block can never be executed either. Thus, these `try` statements can be removed completely. Loading history...
35
36			// @todo
37			} catch (Exception $e) {
			0 ignored issues – show Unused Code introduced 2016-11-26 10:01 UTC by Report Bug Copy Issue Report `catch (\Exception $e) { ...0, $e->getMessage()); }` does not seem to be reachable. This check looks for unreachable code. It uses sophisticated control flow analysis techniques to find statements which will never be executed. Unreachable code is most often the result of `return`, `die` or `exit` statements that have been added for debug purposes. function fx() { try { doSomething(); return true; } catch (\Exception $e) { return false; } return false; } In the above example, the last `return false` will never be executed, because a return statement has already been met in every possible execution path. Loading history...
38			Log::error($e->getMessage());
39
40			abort(500, $e->getMessage());
41			}
42			}
43
44			/**
45			* Create a new cart.
46			*
47			* @param \Bedard\Shop\Repositories\CartRepository $repository
48			* @return \Bedard\Shop\Models\Cart
49			*/
50			public function store(CartRepository $repository)
51			{
52			try {
			0 ignored issues – show Unused Code introduced 2016-11-28 15:48 UTC by Report Bug Copy Issue Report This `try` statement is empty and can be removed. This check looks for `try` blocks that have no statements or where all statements have been commented out. This may be the result of changes for debugging or the code may simply be obsolete. If there is nothing in the `try` then the `catch` block can never be executed either. Thus, these `try` statements can be removed completely. Loading history...
53
54			// @todo
55			} catch (Exception $e) {
			0 ignored issues – show Unused Code introduced 2016-11-26 10:01 UTC by Report Bug Copy Issue Report `catch (\Exception $e) { ...0, $e->getMessage()); }` does not seem to be reachable. This check looks for unreachable code. It uses sophisticated control flow analysis techniques to find statements which will never be executed. Unreachable code is most often the result of `return`, `die` or `exit` statements that have been added for debug purposes. function fx() { try { doSomething(); return true; } catch (\Exception $e) { return false; } return false; } In the above example, the last `return false` will never be executed, because a return statement has already been met in every possible execution path. Loading history...
56			Log::error($e->getMessage());
57
58			abort(500, $e->getMessage());
59			}
60			}
61			}
62

scottbedard / oc-shop-plugin

Push — master ( 725f0a...f82868 )

Cart A

Complexity

Size/Duplication

Coupling/Cohesion

Importance

3 Methods

Duplication Side-by-Side

Filter issues like