Passed
Push — feature/bilingualism-declarati... ( eda03c...7ce11e )
by Xander
28:57 queued 17:01
created

DemoController::reviewApplications()   A

Complexity

Conditions 2
Paths 2

Size

Total Lines 21
Code Lines 12

Duplication

Lines 0
Ratio 0 %

Code Coverage

Tests 0
CRAP Score 6

Importance

Changes 0
Metric Value
eloc 12
dl 0
loc 21
ccs 0
cts 13
cp 0
rs 9.8666
c 0
b 0
f 0
cc 2
nc 2
nop 0
crap 6
1
<?php
2
0 ignored issues
show
Coding Style introduced by
Missing file doc comment
Loading history...
3
namespace App\Http\Controllers;
4
5
use Illuminate\Support\Facades\Lang;
6
use App\Models\JobPoster;
7
use App\Models\JobApplication;
8
9
class DemoController extends Controller
0 ignored issues
show
Coding Style introduced by
Missing doc comment for class DemoController
Loading history...
10
{
11
    /**
12
     * Display a listing of the applicants to specified job.
13
     *
14
     * @return \Illuminate\Http\Response
15
     */
16
    public function reviewApplications()
17
    {
18
        if (\App::environment('local')) {
0 ignored issues
show
Unused Code introduced by
The call to Illuminate\Support\Facades\App::environment() has too many arguments starting with 'local'. ( Ignorable by Annotation )

If this is a false-positive, you can also ignore this issue in your code via the ignore-call  annotation

18
        if (\App::/** @scrutinizer ignore-call */ environment('local')) {

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress. Please note the @ignore annotation hint above.

Loading history...
19
            $jobPoster = factory(JobPoster::class)->state('closed')->create();
20
            $applications = factory(JobApplication::class, 10)->create([
0 ignored issues
show
Coding Style introduced by
The opening parenthesis of a multi-line function call should be the last content on the line.
Loading history...
21
                'job_poster_id' => $jobPoster->id
22
            ]);
0 ignored issues
show
Coding Style introduced by
For multi-line function calls, the closing parenthesis should be on a new line.

If a function call spawns multiple lines, the coding standard suggests to move the closing parenthesis to a new line:

someFunctionCall(
    $firstArgument,
    $secondArgument,
    $thirdArgument
); // Closing parenthesis on a new line.
Loading history...
23
            $jobPoster->submitted_applications()->saveMany($applications);
24
25
            $applications->load(['veteran_status', 'citizenship_declaration', 'application_review', "applicant.user"]);
26
            return view('manager/review_applications', [
1 ignored issue
show
Bug Best Practice introduced by
The expression return view('manager/rev...s\ReviewStatus::all())) returns the type Illuminate\View\View which is incompatible with the documented return type Illuminate\Http\Response.
Loading history...
Coding Style introduced by
The opening parenthesis of a multi-line function call should be the last content on the line.
Loading history...
27
                /*Localization Strings*/
28
                'jobs_l10n' => Lang::get('manager/job_index'),
29
30
                /* Data */
31
                'job' => $jobPoster,
32
                'applications' => $applications,
33
                'review_statuses' => ReviewStatus::all(),
34
            ]);
0 ignored issues
show
Coding Style introduced by
For multi-line function calls, the closing parenthesis should be on a new line.

If a function call spawns multiple lines, the coding standard suggests to move the closing parenthesis to a new line:

someFunctionCall(
    $firstArgument,
    $secondArgument,
    $thirdArgument
); // Closing parenthesis on a new line.
Loading history...
35
        }
36
        return null;
37
    }
38
}
39