1 | <?php |
||||
2 | |||||
3 | use Illuminate\Support\Facades\Route; |
||||
4 | |||||
5 | if (config('electrum.web_interface.enabled', false)) { |
||||
6 | Route::prefix(config('electrum.web_interface.prefix', 'electrum'))->group(function () { |
||||
0 ignored issues
–
show
|
|||||
7 | Route::get('/', 'AraneaDev\Electrum\App\IndexController'); |
||||
8 | |||||
9 | Route::prefix('api')->group(function () { |
||||
0 ignored issues
–
show
The call to
Illuminate\Support\Facades\Route::group() has too few arguments starting with routes .
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
This check compares calls to functions or methods with their respective definitions. If the call has less 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. ![]() |
|||||
10 | Route::get('status', 'AraneaDev\Electrum\App\Api\StatusController'); |
||||
11 | |||||
12 | Route::get('history', 'AraneaDev\Electrum\App\Api\HistoryController@index'); |
||||
13 | Route::get('history/{address}', 'AraneaDev\Electrum\App\Api\HistoryController@show'); |
||||
14 | Route::get('history/tx/{txid}', 'AraneaDev\Electrum\App\Api\HistoryController@details'); |
||||
15 | |||||
16 | Route::get('addresses', 'AraneaDev\Electrum\App\Api\AddressController@index'); |
||||
17 | Route::get('addresses/unused', 'AraneaDev\Electrum\App\Api\AddressController@unused'); |
||||
18 | Route::get('addresses/is_mine{address}', 'AraneaDev\Electrum\App\Api\AddressController@is_mine'); |
||||
19 | Route::get('addresses/{address}', 'AraneaDev\Electrum\App\Api\AddressController@check'); |
||||
20 | |||||
21 | Route::prefix('requests')->group(function () { |
||||
0 ignored issues
–
show
The call to
Illuminate\Support\Facades\Route::group() has too few arguments starting with routes .
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
This check compares calls to functions or methods with their respective definitions. If the call has less 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. ![]() |
|||||
22 | Route::get('/', 'AraneaDev\Electrum\App\Api\RequestsController@index'); |
||||
23 | Route::get('{address}', 'AraneaDev\Electrum\App\Api\RequestsController@show'); |
||||
24 | |||||
25 | Route::post('/', 'AraneaDev\Electrum\App\Api\RequestsController@create'); |
||||
26 | |||||
27 | Route::delete('/', 'AraneaDev\Electrum\App\Api\RequestsController@clear'); |
||||
28 | Route::delete('{address}', 'AraneaDev\Electrum\App\Api\RequestsController@destroy'); |
||||
29 | }); |
||||
30 | }); |
||||
31 | }); |
||||
32 | } |
||||
33 |
This check compares calls to functions or methods with their respective definitions. If the call has less 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.