Skip to content
This repository has been archived by the owner on Sep 12, 2024. It is now read-only.

Release 3.0.0

Release 3.0.0 #191

Triggered via pull request October 25, 2023 03:29
Status Failure
Total duration 1m 8s
Artifacts

pr.yml

on: pull_request
Changelog should be updated
4s
Changelog should be updated
Validate composer
11s
Validate composer
runner-phpcs
19s
runner-phpcs
PHP-CS-FIXER
31s
PHP-CS-FIXER
TwigCS
20s
TwigCS
JS coding standards
58s
JS coding standards
Tests
32s
Tests
Fit to window
Zoom out
Zoom in

Annotations

38 errors and 2 warnings
[PHPCS] core/Service/DatafordelerService.php#L7: core/Service/DatafordelerService.php#L7
Missing doc comment for class DatafordelerService
[PHPCS] core/Service/DatafordelerService.php#L11: core/Service/DatafordelerService.php#L11
Missing doc comment for function __construct()
[PHPCS] core/Service/DatafordelerService.php#L16: core/Service/DatafordelerService.php#L16
Missing doc comment for function getPersonData()
[PHPCS] core/CPR/ServiceplatformenCprService.php#L27: core/CPR/ServiceplatformenCprService.php#L27
Doc comment for parameter $dataFordelerController does not match actual variable name $httpClient
[PHPCS] core/CPR/ServiceplatformenCprService.php#L28: core/CPR/ServiceplatformenCprService.php#L28
Expected 4 spaces after parameter type; 1 found
[PHPCS] core/Controller/ProcessReminderController.php#L22: core/Controller/ProcessReminderController.php#L22
There must be one blank line after the last USE statement; 0 found;
[PHPCS] core/Controller/ProcessReminderController.php#L47: core/Controller/ProcessReminderController.php#L47
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/ProcessReminderController.php#L50: core/Controller/ProcessReminderController.php#L50
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/ProcessReminderController.php#L96: core/Controller/ProcessReminderController.php#L96
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/ProcessReminderController.php#L99: core/Controller/ProcessReminderController.php#L99
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/ProcessClientController.php#L71: core/Controller/ProcessClientController.php#L71
Doc comment for parameter $datafordelerHttpClient does not match actual variable name $datafordelerService
[PHPCS] core/Controller/ProcessClientController.php#L98: core/Controller/ProcessClientController.php#L98
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/ProcessClientController.php#L101: core/Controller/ProcessClientController.php#L101
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/ProcessClientController.php#L157: core/Controller/ProcessClientController.php#L157
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/ProcessClientController.php#L160: core/Controller/ProcessClientController.php#L160
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/JournalEntryController.php#L28: core/Controller/JournalEntryController.php#L28
There must be one blank line after the last USE statement; 0 found;
[PHPCS] core/Controller/JournalEntryController.php#L159: core/Controller/JournalEntryController.php#L159
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/JournalEntryController.php#L162: core/Controller/JournalEntryController.php#L162
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/JournalEntryController.php#L210: core/Controller/JournalEntryController.php#L210
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/JournalEntryController.php#L213: core/Controller/JournalEntryController.php#L213
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/JournalEntryController.php#L269: core/Controller/JournalEntryController.php#L269
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/JournalEntryController.php#L272: core/Controller/JournalEntryController.php#L272
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/JournalEntryController.php#L334: core/Controller/JournalEntryController.php#L334
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/JournalEntryController.php#L337: core/Controller/JournalEntryController.php#L337
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/ProcessController.php#L324: core/Controller/ProcessController.php#L324
Doc comment for parameter $datafordelerHttpClient does not match actual variable name $datafordelerService
[PHPCS] core/Controller/ProcessController.php#L342: core/Controller/ProcessController.php#L342
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/ProcessController.php#L345: core/Controller/ProcessController.php#L345
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/ProcessController.php#L393: core/Controller/ProcessController.php#L393
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/ProcessController.php#L396: core/Controller/ProcessController.php#L396
Use Yoda conditions when checking a variable against an expression to avoid an accidental assignment inside the condition statement.
[PHPCS] core/Controller/DatafordelerController.php#L15: core/Controller/DatafordelerController.php#L15
There must be one blank line after the last USE statement; 0 found;
[PHPCS] core/Controller/VisitationController.php#L70: core/Controller/VisitationController.php#L70
Doc comment for parameter "$datafordelerService" missing
[PHPCS] core/Controller/VisitationController.php#L74: core/Controller/VisitationController.php#L74
Doc comment for parameter $datafordelerHttpClient does not match actual variable name $datafordelerService
TwigCS
Process completed with exit code 1.
PHP-CS-FIXER
Process completed with exit code 8.
Changelog should be updated
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
JS coding standards
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/