DepartmentController::get_departments() - Code Metrics - Inspection of "Nightly build" - idevelopment/RingMe - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Push — master ( 37b68a...dd2f56 )

by Glenn

created 2016-05-21 00:31 UTC

DepartmentController::get_departments() A

↳ Parent: DepartmentController

Complexity

Conditions	2
Paths	2

Size

Total Lines	14
Code Lines	8

Duplication

Lines	14
Ratio	100 %

Importance

Changes	1
Bugs	0	Features	0

Metric	Value
c	1
b	0
f	0
dl	14
loc	14
rs	9.4285
cc	2
eloc	8
nc	2
nop	0

<?php

namespace App\Http\Controllers;

use App\Departments;
use Illuminate\Http\Request;

use App\Http\Requests;

/**
 * Class DepartmentController
 * @package App\Http\Controllers
 *
 * TODO: the controller needs phpunit testing.
 */
class DepartmentController extends Controller
{
    /**
     * DepartmentController constructor.
     */
    public function __construct()
    {
        $this->middleware('auth');
        $this->middleware('lang');
    }

    /**
     * Display a listing of the resource.
     *
     * @return \Illuminate\Http\Response
     */
    public function index()
    {
        $data['query'] = Departments::paginate(15);
foreach ($collection as $item) {
    $myArray['foo'] = $item->getFoo();

    if ($item->hasBar()) {
        $myArray['bar'] = $item->getBar();
    }

    // do something with $myArray
}
        return view('departments.index', $data);
    }

    /**
     * Show the form for creating a new resource.
     *
     * @return \Illuminate\Http\Response
     */
    public function create()
    {
        return view('departments.insert');
    }

    /**
     * Store a newly created resource in storage.
     *
     * @param  Requests\DepartmentsValidator $input
     * @return \Illuminate\Http\Response
     */
    public function store(Requests\DepartmentsValidator $input)
    {
        Departments::create($input->except('_token'));
        return redirect()->route('departments.index');
    }

    /**
     * Display the specified resource.
     *
     * @param  int  $id the department id in the database.
     * @return \Illuminate\Http\Response
     */
    public function show($id)
    {
        $data['query'] = Departments::find($id);
foreach ($collection as $item) {
    $myArray['foo'] = $item->getFoo();

    if ($item->hasBar()) {
        $myArray['bar'] = $item->getBar();
    }

    // do something with $myArray
}
        return view('departments.specific', $data);
    }

    /**
     * Show the form for editing the specified resource.
     *
     * @param  int  $id the department id in the database.
     * @return \Illuminate\Http\Response
     */
    public function edit($id)
    {
        $data['query'] = Departments::find($id);
foreach ($collection as $item) {
    $myArray['foo'] = $item->getFoo();

    if ($item->hasBar()) {
        $myArray['bar'] = $item->getBar();
    }

    // do something with $myArray
}
        return view('departments.update', $data);
    }

    /**
     * Update the specified resource in storage.
     *
     * @param  Requests\DepartmentsValidator $input
     * @param  int $id the department id in the database.
     * @return \Illuminate\Http\Response
     */
    public function update(Requests\DepartmentsValidator $input, $id)
    {
        Departments::find($id)->update($input->except('_token'));
        return redirect()->route('departments.index');
    }

    /**
     * Remove the specified resource from storage.
     *
     * @param  int  $id the department id in the database.
     * @return \Illuminate\Http\Response
     */
    public function destroy($id)
    {
        Departments::destroy($id);
        return redirect()->back(302);
    }

    public function get_departments()

    {
        $items = Departments::all();
        $data2 = [];
        foreach($items as $department)
        {
         $data2[] = [
        'value' => $department["id"],
        'text'  => $department["name"]
        ];

        }
        return json_encode($data2);
    }    
}


1		<?php
2
3		namespace App\Http\Controllers;
4
5		use App\Departments;
6		use Illuminate\Http\Request;
7
8		use App\Http\Requests;
9
10		/**
11		* Class DepartmentController
12		* @package App\Http\Controllers
13		*
14		* TODO: the controller needs phpunit testing.
15		*/
16		class DepartmentController extends Controller
17		{
18		/**
19		* DepartmentController constructor.
20		*/
21		public function __construct()
22		{
23		$this->middleware('auth');
24		$this->middleware('lang');
25		}
26
27		/**
28		* Display a listing of the resource.
29		*
30		* @return \Illuminate\Http\Response
31		*/
32		public function index()
33		{
34		$data['query'] = Departments::paginate(15);
		0 ignored issues – show Coding Style Comprehensibility introduced 2016-05-19 11:18 UTC by Report Bug Copy Issue Report `$data` was never initialized. Although not strictly required by PHP, it is generally a good practice to add `$data = array();` before regardless. Adding an explicit array definition is generally preferable to implicit array definition as it guarantees a stable state of the code. Let’s take a look at an example: foreach ($collection as $item) { $myArray['foo'] = $item->getFoo(); if ($item->hasBar()) { $myArray['bar'] = $item->getBar(); } // do something with $myArray } As you can see in this example, the array `$myArray` is initialized the first time when the foreach loop is entered. You can also see that the value of the `bar` key is only written conditionally; thus, its value might result from a previous iteration. This might or might not be intended. To make your intention clear, your code more readible and to avoid accidental bugs, we recommend to add an explicit initialization `$myArray = array()` either outside or inside the foreach loop. Loading history...
35		return view('departments.index', $data);
36		}
37
38		/**
39		* Show the form for creating a new resource.
40		*
41		* @return \Illuminate\Http\Response
42		*/
43		public function create()
44		{
45		return view('departments.insert');
46		}
47
48		/**
49		* Store a newly created resource in storage.
50		*
51		* @param Requests\DepartmentsValidator $input
52		* @return \Illuminate\Http\Response
53		*/
54		public function store(Requests\DepartmentsValidator $input)
55		{
56		Departments::create($input->except('_token'));
57		return redirect()->route('departments.index');
58		}
59
60		/**
61		* Display the specified resource.
62		*
63		* @param int $id the department id in the database.
64		* @return \Illuminate\Http\Response
65		*/
66		public function show($id)
67		{
68		$data['query'] = Departments::find($id);
		0 ignored issues – show Coding Style Comprehensibility introduced 2016-05-19 11:18 UTC by Report Bug Copy Issue Report `$data` was never initialized. Although not strictly required by PHP, it is generally a good practice to add `$data = array();` before regardless. Adding an explicit array definition is generally preferable to implicit array definition as it guarantees a stable state of the code. Let’s take a look at an example: foreach ($collection as $item) { $myArray['foo'] = $item->getFoo(); if ($item->hasBar()) { $myArray['bar'] = $item->getBar(); } // do something with $myArray } As you can see in this example, the array `$myArray` is initialized the first time when the foreach loop is entered. You can also see that the value of the `bar` key is only written conditionally; thus, its value might result from a previous iteration. This might or might not be intended. To make your intention clear, your code more readible and to avoid accidental bugs, we recommend to add an explicit initialization `$myArray = array()` either outside or inside the foreach loop. Loading history...
69		return view('departments.specific', $data);
70		}
71
72		/**
73		* Show the form for editing the specified resource.
74		*
75		* @param int $id the department id in the database.
76		* @return \Illuminate\Http\Response
77		*/
78		public function edit($id)
79		{
80		$data['query'] = Departments::find($id);
		0 ignored issues – show Coding Style Comprehensibility introduced 2016-05-19 11:18 UTC by Report Bug Copy Issue Report `$data` was never initialized. Although not strictly required by PHP, it is generally a good practice to add `$data = array();` before regardless. Adding an explicit array definition is generally preferable to implicit array definition as it guarantees a stable state of the code. Let’s take a look at an example: foreach ($collection as $item) { $myArray['foo'] = $item->getFoo(); if ($item->hasBar()) { $myArray['bar'] = $item->getBar(); } // do something with $myArray } As you can see in this example, the array `$myArray` is initialized the first time when the foreach loop is entered. You can also see that the value of the `bar` key is only written conditionally; thus, its value might result from a previous iteration. This might or might not be intended. To make your intention clear, your code more readible and to avoid accidental bugs, we recommend to add an explicit initialization `$myArray = array()` either outside or inside the foreach loop. Loading history...
81		return view('departments.update', $data);
82		}
83
84		/**
85		* Update the specified resource in storage.
86		*
87		* @param Requests\DepartmentsValidator $input
88		* @param int $id the department id in the database.
89		* @return \Illuminate\Http\Response
90		*/
91		public function update(Requests\DepartmentsValidator $input, $id)
92		{
93		Departments::find($id)->update($input->except('_token'));
94		return redirect()->route('departments.index');
95		}
96
97		/**
98		* Remove the specified resource from storage.
99		*
100		* @param int $id the department id in the database.
101		* @return \Illuminate\Http\Response
102		*/
103		public function destroy($id)
104		{
105		Departments::destroy($id);
106		return redirect()->back(302);
107		}
108
109	View Code Duplication	public function get_departments()
		0 ignored issues – show Duplication introduced 2016-05-21 00:33 UTC by Report Bug Copy Issue Report This method seems to be duplicated in your project. Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation. You can also find more detailed suggestions in the “Code” section of your repository. Loading history...
110		{
111		$items = Departments::all();
112		$data2 = [];
113		foreach($items as $department)
114		{
115		$data2[] = [
116		'value' => $department["id"],
117		'text' => $department["name"]
118		];
119
120		}
121		return json_encode($data2);
122		}
123		}
124

idevelopment / RingMe

Push — master ( 37b68a...dd2f56 )

DepartmentController::get_departments() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like