This project does not seem to handle request data directly as such no vulnerable execution paths were found.
include
, or for example
via PHP's auto-loading mechanism.
These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
2 | |||
3 | namespace Bantenprov\User\Http\Controllers; |
||
4 | |||
5 | /* Require */ |
||
6 | use App\Http\Controllers\Controller; |
||
7 | use Illuminate\Http\Request; |
||
8 | use Bantenprov\User\Facades\UserFacade; |
||
9 | |||
10 | /* Models */ |
||
11 | use App\User; |
||
12 | use App\Role; |
||
13 | |||
14 | /* Etc */ |
||
15 | use Validator; |
||
16 | |||
17 | /** |
||
18 | * The UserController class. |
||
19 | * |
||
20 | * @package Bantenprov\User |
||
21 | * @author bantenprov <[email protected]> |
||
22 | */ |
||
23 | class UserController extends Controller |
||
24 | { |
||
25 | /** |
||
26 | * Create a new controller instance. |
||
27 | * |
||
28 | * @return void |
||
0 ignored issues
–
show
|
|||
29 | */ |
||
30 | public function __construct(User $user, Role $role) |
||
31 | { |
||
32 | $this->user = $user; |
||
33 | $this->role = $role; |
||
34 | } |
||
35 | |||
36 | /** |
||
37 | * Display a listing of the resource. |
||
38 | * |
||
39 | * @return \Illuminate\Http\Response |
||
40 | */ |
||
41 | public function index(Request $request) |
||
42 | { |
||
43 | if (request()->has('sort')) { |
||
44 | list($sortCol, $sortDir) = explode('|', request()->sort); |
||
45 | |||
46 | $query = $this->user->orderBy($sortCol, $sortDir); |
||
47 | } else { |
||
48 | $query = $this->user->orderBy('id', 'asc'); |
||
49 | } |
||
50 | |||
51 | if ($request->exists('filter')) { |
||
52 | $query->where(function($q) use($request) { |
||
53 | $value = "%{$request->filter}%"; |
||
54 | $q->where('name', 'like', $value) |
||
55 | ->orWhere('email', 'like', $value); |
||
56 | }); |
||
57 | } |
||
58 | |||
59 | $perPage = request()->has('per_page') ? (int) request()->per_page : null; |
||
60 | $response = $query->with('roles')->paginate($perPage); |
||
61 | |||
62 | return response()->json($response) |
||
63 | ->header('Access-Control-Allow-Origin', '*') |
||
64 | ->header('Access-Control-Allow-Methods', 'GET'); |
||
65 | } |
||
66 | |||
67 | /** |
||
68 | * Show the form for creating a new resource. |
||
69 | * |
||
70 | * @return \Illuminate\Http\Response |
||
71 | */ |
||
72 | public function create() |
||
73 | { |
||
74 | $user = $this->user; |
||
75 | |||
76 | $response['user'] = $user; |
||
0 ignored issues
–
show
Coding Style
Comprehensibility
introduced
by
$response was never initialized. Although not strictly required by PHP, it is generally a good practice to add $response = 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 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. ![]() |
|||
77 | $response['status'] = true; |
||
78 | |||
79 | return response()->json($user); |
||
80 | } |
||
81 | |||
82 | /** |
||
83 | * Display the specified resource. |
||
84 | * |
||
85 | * @param \App\User $user |
||
0 ignored issues
–
show
There is no parameter named
$user . Was it maybe removed?
This check looks for PHPDoc comments describing methods or function parameters that do not exist on the corresponding method or function. Consider the following example. The parameter /**
* @param array $germany
* @param array $island
* @param array $italy
*/
function finale($germany, $island) {
return "2:1";
}
The most likely cause is that the parameter was removed, but the annotation was not. ![]() |
|||
86 | * @return \Illuminate\Http\Response |
||
87 | */ |
||
88 | public function store(Request $request) |
||
89 | { |
||
90 | $user = $this->user; |
||
91 | |||
92 | $validator = Validator::make($request->all(), [ |
||
93 | 'name' => 'required|unique:users,name', |
||
94 | 'email' => 'required|email|unique:users,email', |
||
95 | 'password' => 'required', |
||
96 | ]); |
||
97 | |||
98 | if($validator->fails()){ |
||
99 | $response['message'] = 'Failed, name or email already exists'; |
||
0 ignored issues
–
show
Coding Style
Comprehensibility
introduced
by
$response was never initialized. Although not strictly required by PHP, it is generally a good practice to add $response = 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 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. ![]() |
|||
100 | } else { |
||
101 | $user->name = $request->input('name'); |
||
102 | $user->email = $request->input('email'); |
||
103 | $user->password = bcrypt($request->input('password')); |
||
104 | $user->save(); |
||
105 | |||
106 | $response['message'] = 'success'; |
||
0 ignored issues
–
show
Coding Style
Comprehensibility
introduced
by
$response was never initialized. Although not strictly required by PHP, it is generally a good practice to add $response = 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 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. ![]() |
|||
107 | } |
||
108 | |||
109 | $response['status'] = true; |
||
110 | |||
111 | return response()->json($response); |
||
112 | } |
||
113 | |||
114 | /** |
||
115 | * Store a newly created resource in storage. |
||
116 | * |
||
117 | * @param \Illuminate\Http\Request $request |
||
0 ignored issues
–
show
There is no parameter named
$request . Was it maybe removed?
This check looks for PHPDoc comments describing methods or function parameters that do not exist on the corresponding method or function. Consider the following example. The parameter /**
* @param array $germany
* @param array $island
* @param array $italy
*/
function finale($germany, $island) {
return "2:1";
}
The most likely cause is that the parameter was removed, but the annotation was not. ![]() |
|||
118 | * @return \Illuminate\Http\Response |
||
119 | */ |
||
120 | View Code Duplication | public function show($id) |
|
0 ignored issues
–
show
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. ![]() |
|||
121 | { |
||
122 | $user = $this->user->findOrFail($id); |
||
123 | |||
124 | $response['user'] = $user; |
||
0 ignored issues
–
show
Coding Style
Comprehensibility
introduced
by
$response was never initialized. Although not strictly required by PHP, it is generally a good practice to add $response = 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 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. ![]() |
|||
125 | $response['status'] = true; |
||
126 | |||
127 | return response()->json($response); |
||
128 | } |
||
129 | |||
130 | /** |
||
131 | * Show the form for editing the specified resource. |
||
132 | * |
||
133 | * @param \App\User $user |
||
0 ignored issues
–
show
There is no parameter named
$user . Was it maybe removed?
This check looks for PHPDoc comments describing methods or function parameters that do not exist on the corresponding method or function. Consider the following example. The parameter /**
* @param array $germany
* @param array $island
* @param array $italy
*/
function finale($germany, $island) {
return "2:1";
}
The most likely cause is that the parameter was removed, but the annotation was not. ![]() |
|||
134 | * @return \Illuminate\Http\Response |
||
135 | */ |
||
136 | View Code Duplication | public function edit($id) |
|
0 ignored issues
–
show
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. ![]() |
|||
137 | { |
||
138 | $user = $this->user->findOrFail($id); |
||
139 | |||
140 | $response['user'] = $user; |
||
0 ignored issues
–
show
Coding Style
Comprehensibility
introduced
by
$response was never initialized. Although not strictly required by PHP, it is generally a good practice to add $response = 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 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. ![]() |
|||
141 | $response['status'] = true; |
||
142 | |||
143 | return response()->json($response); |
||
144 | } |
||
145 | |||
146 | /** |
||
147 | * Update the specified resource in storage. |
||
148 | * |
||
149 | * @param \Illuminate\Http\Request $request |
||
150 | * @param \App\User $user |
||
0 ignored issues
–
show
There is no parameter named
$user . Was it maybe removed?
This check looks for PHPDoc comments describing methods or function parameters that do not exist on the corresponding method or function. Consider the following example. The parameter /**
* @param array $germany
* @param array $island
* @param array $italy
*/
function finale($germany, $island) {
return "2:1";
}
The most likely cause is that the parameter was removed, but the annotation was not. ![]() |
|||
151 | * @return \Illuminate\Http\Response |
||
152 | */ |
||
153 | public function update(Request $request, $id) |
||
154 | { |
||
155 | $user = $this->user->findOrFail($id); |
||
156 | |||
157 | if ($request->input('old_name') == $request->input('name') || $request->input('old_email') == $request->input('email')) |
||
158 | { |
||
159 | $validator = Validator::make($request->all(), [ |
||
160 | 'name' => 'required', |
||
161 | 'email' => 'email|required', |
||
162 | ]); |
||
163 | } else { |
||
164 | $validator = Validator::make($request->all(), [ |
||
165 | 'name' => 'required|unique:users,name', |
||
166 | 'email' => 'email|required|unique:users,email', |
||
167 | ]); |
||
168 | } |
||
169 | |||
170 | if ($validator->fails()) { |
||
171 | $response['message'] = 'failed, user or email already exist'; |
||
0 ignored issues
–
show
Coding Style
Comprehensibility
introduced
by
$response was never initialized. Although not strictly required by PHP, it is generally a good practice to add $response = 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 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. ![]() |
|||
172 | } else { |
||
173 | if($request->input('password') == ""){ |
||
174 | $user->name = $request->input('name'); |
||
175 | $user->email = $request->input('email'); |
||
176 | $user->save(); |
||
177 | }else{ |
||
178 | $user->name = $request->input('name'); |
||
179 | $user->email = $request->input('email'); |
||
180 | $user->password = bcrypt($request->input('password')); |
||
181 | $user->save(); |
||
182 | } |
||
183 | |||
184 | |||
185 | $response['message'] = 'success'; |
||
0 ignored issues
–
show
Coding Style
Comprehensibility
introduced
by
$response was never initialized. Although not strictly required by PHP, it is generally a good practice to add $response = 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 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. ![]() |
|||
186 | } |
||
187 | |||
188 | $response['status'] = true; |
||
189 | |||
190 | return response()->json($response); |
||
191 | } |
||
192 | |||
193 | public function userAddRole($user_id) |
||
194 | { |
||
195 | |||
196 | $user = $this->user->with('roles')->find($user_id); |
||
197 | |||
198 | $roles = $this->role->all(); |
||
199 | |||
200 | $response['roles'] = $roles; |
||
0 ignored issues
–
show
Coding Style
Comprehensibility
introduced
by
$response was never initialized. Although not strictly required by PHP, it is generally a good practice to add $response = 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 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. ![]() |
|||
201 | $response['user'] = $user; |
||
202 | $response['status'] = true; |
||
203 | |||
204 | return response()->json($response); |
||
205 | |||
206 | } |
||
207 | |||
208 | public function userStoreRole($user_id, Request $request) |
||
209 | { |
||
210 | if(\Auth::user()->hasRole(['superadministrator'])){ |
||
211 | if($request->new_role != ''){ |
||
212 | $this->user->find($user_id)->detachRole($request->old_role); |
||
213 | $this->user->find($user_id)->attachRole($request->new_role); |
||
214 | } |
||
215 | $message = 'Update role berhasil.'; |
||
216 | $typem = 'success'; |
||
217 | $title = 'Success'; |
||
218 | }else{ |
||
219 | $title = 'Failed'; |
||
220 | $typem = 'error'; |
||
221 | $message = 'Anda tidak memiliki hak akses untuk ini.'; |
||
222 | } |
||
223 | |||
224 | $response['title'] = $title; |
||
0 ignored issues
–
show
Coding Style
Comprehensibility
introduced
by
$response was never initialized. Although not strictly required by PHP, it is generally a good practice to add $response = 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 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. ![]() |
|||
225 | $response['typem'] = $typem; |
||
226 | $response['message'] = $message; |
||
227 | $response['status'] = true; |
||
228 | |||
229 | return response()->json($response); |
||
230 | |||
231 | } |
||
232 | |||
233 | public function removeRole($user_id) |
||
234 | { |
||
235 | $user = $this->user->with('roles')->find($user_id); |
||
236 | |||
237 | if($user->roles->count() > 0){ |
||
238 | foreach ($user->roles as $role) { |
||
239 | $this->user->detachRole($role->id); |
||
240 | } |
||
241 | } |
||
242 | |||
243 | } |
||
244 | |||
245 | /** |
||
246 | * Remove the specified resource from storage. |
||
247 | * |
||
248 | * @param \App\User $user |
||
0 ignored issues
–
show
There is no parameter named
$user . Was it maybe removed?
This check looks for PHPDoc comments describing methods or function parameters that do not exist on the corresponding method or function. Consider the following example. The parameter /**
* @param array $germany
* @param array $island
* @param array $italy
*/
function finale($germany, $island) {
return "2:1";
}
The most likely cause is that the parameter was removed, but the annotation was not. ![]() |
|||
249 | * @return \Illuminate\Http\Response |
||
250 | */ |
||
251 | View Code Duplication | public function destroy($id) |
|
0 ignored issues
–
show
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. ![]() |
|||
252 | { |
||
253 | |||
254 | $user = $this->user->findOrFail($id); |
||
255 | |||
256 | $this->removeRole($id); |
||
257 | |||
258 | if ($user->delete()) { |
||
259 | $response['status'] = true; |
||
0 ignored issues
–
show
Coding Style
Comprehensibility
introduced
by
$response was never initialized. Although not strictly required by PHP, it is generally a good practice to add $response = 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 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. ![]() |
|||
260 | } else { |
||
261 | $response['status'] = false; |
||
0 ignored issues
–
show
Coding Style
Comprehensibility
introduced
by
$response was never initialized. Although not strictly required by PHP, it is generally a good practice to add $response = 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 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. ![]() |
|||
262 | } |
||
263 | |||
264 | return json_encode($response); |
||
265 | } |
||
266 | } |
||
267 |
Adding a
@return
annotation to a constructor is not recommended, since a constructor does not have a meaningful return value.Please refer to the PHP core documentation on constructors.