APIFullUsersController   A
last analyzed

Complexity

Total Complexity 8

Size/Duplication

Total Lines 113
Duplicated Lines 8.85 %

Coupling/Cohesion

Components 1
Dependencies 6

Importance

Changes 1
Bugs 0 Features 0
Metric Value
c 1
b 0
f 0
dl 10
loc 113
rs 10
wmc 8
lcom 1
cbo 6

8 Methods

Rating   Name   Duplication   Size   Complexity  
A index() 0 5 1
A store() 0 12 1
A massiveDestroy() 0 5 1
A executeDestroy() 10 10 1
A destroy() 0 6 1
A show() 0 5 1
A update() 0 6 1
A registerByEmail() 0 5 1

How to fix   Duplicated Code   

Duplicated Code

Duplicate code is one of the most pungent code smells. A rule that is often used is to re-structure code once it is duplicated in three or more places.

Common duplication problems, and corresponding solutions are:

1
<?php
2
3
namespace Acacha\Users\Http\Controllers;
4
5
use Acacha\Users\Events\UserCreated;
6
use Acacha\Users\Events\UserRemoved;
7
use Acacha\Users\Http\Requests\CreateUserRequest;
8
use Acacha\Users\Http\Requests\MassiveDestroyRequest;
9
use Acacha\Users\Http\Requests\UpdateUserRequest;
10
use App\User;
11
use Illuminate\Http\JsonResponse;
12
use Illuminate\Http\Request;
13
use Password;
14
use Response;
15
16
/**
17
 * Class APIFullUsersController
18
 *
19
 * @package Acacha\Users\Http\Controllers
20
 */
21
class APIFullUsersController extends Controller
22
{
23
    /**
24
     * Display a listing of the resource.
25
     *
26
     * @return \Illuminate\Http\Response
27
     */
28
    public function index()
29
    {
30
        $this->authorize('list-users');
31
        return User::paginate();
32
    }
33
34
    /**
35
     * Store a newly created resource in storage.
36
     *
37
     * @param CreateUserRequest $request
38
     * @return \Illuminate\Http\JsonResponse
39
     */
40
    public function store(CreateUserRequest $request)
41
    {
42
        $user = User::create([
43
            'name' => $request->input('name'),
44
            'email' => $request->input('email'),
45
            'password' => bcrypt($request->input('password')),
0 ignored issues
show
Bug introduced by
It seems like $request->input('password') targeting Illuminate\Http\Concerns...ractsWithInput::input() can also be of type array; however, bcrypt() does only seem to accept string, maybe add an additional type check?

This check looks at variables that are passed out again to other methods.

If the outgoing method call has stricter type requirements than the method itself, an issue is raised.

An additional type check may prevent trouble.

Loading history...
46
        ]);
47
48
        event(new UserCreated($user));
49
50
        return Response::json(['created' => true ]);
51
    }
52
53
    /**
54
     * Massive destroy.
55
     *
56
     * @param MassiveDestroyRequest $request
57
     * @return \Illuminate\Http\JsonResponse
58
     */
59
    public function massiveDestroy(MassiveDestroyRequest $request)
60
    {
61
        $this->authorize('massive-delete-users');
62
        return $this->executeDestroy($request->input('ids'));
63
    }
64
65
    /**
66
     * Execute destroy.
67
     *
68
     * @param $ids
69
     * @return \Illuminate\Http\JsonResponse
70
     */
71 View Code Duplication
    private function executeDestroy($ids){
0 ignored issues
show
Duplication introduced by
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...
72
73
        $models = User::find($ids);
74
75
        User::destroy($ids);
76
77
        event(new UserRemoved($models->toJson()));
78
79
        return Response::json(['deleted' => true ]);
80
    }
81
82
    /**
83
     * Remove the specified resource from storage.
84
     *
85
     * @param  int|array  $id
86
     * @return \Illuminate\Http\JsonResponse
87
     */
88
    public function destroy($id)
89
    {
90
        $this->authorize('delete-users');
91
92
        return $this->executeDestroy($id);
93
    }
94
95
    /**
96
     * Display the specified resource.
97
     *
98
     * @param  int  $id
99
     * @return \Illuminate\Http\Response
100
     */
101
    public function show($id)
102
    {
103
        $this->authorize('view-users');
104
        return User::find($id);
105
    }
106
107
    /**
108
     * Update the specified resource in storage.
109
     *
110
     * @param UpdateUserRequest $request
111
     * @param $id
112
     * @return \Illuminate\Http\JsonResponse
113
     */
114
    public function update(UpdateUserRequest $request, $id)
115
    {
116
        $user = User::find($id);
117
        $user->update($request->intersect(['email','name','password']));
0 ignored issues
show
Documentation Bug introduced by
The method intersect does not exist on object<Acacha\Users\Http...ests\UpdateUserRequest>? Since you implemented __call, maybe consider adding a @method annotation.

If you implement __call and you know which methods are available, you can improve IDE auto-completion and static analysis by adding a @method annotation to the class.

This is often the case, when __call is implemented by a parent class and only the child class knows which methods exist:

class ParentClass {
    private $data = array();

    public function __call($method, array $args) {
        if (0 === strpos($method, 'get')) {
            return $this->data[strtolower(substr($method, 3))];
        }

        throw new \LogicException(sprintf('Unsupported method: %s', $method));
    }
}

/**
 * If this class knows which fields exist, you can specify the methods here:
 *
 * @method string getName()
 */
class SomeClass extends ParentClass { }
Loading history...
118
        return Response::json(['updated' => true ]);
119
    }
120
121
    /**
122
     * Register user by email
123
     *
124
     * @param Request $request
125
     * @return \Illuminate\Contracts\View\Factory|\Illuminate\View\View
126
     */
127
    public function registerByEmail(Request $request)
0 ignored issues
show
Unused Code introduced by
The parameter $request is not used and could be removed.

This check looks from parameters that have been defined for a function or method, but which are not used in the method body.

Loading history...
128
    {
129
        $data = [];
130
        return view('acacha_users::register-by-email',$data);
131
    }
132
133
}