Application dates configurable #266
sezanzebAnnotations
10 errors and 3 warnings
|
frontend:
backend/src/services/settings-service.ts#L124
'getDefaultProjectSettings' is declared but its value is never read.
|
|
frontend:
backend/src/services/rating-service.ts#L239
Property 'project' does not exist on type 'Settings'.
|
|
frontend:
backend/src/services/project-service.ts#L75
Property 'project' does not exist on type 'Settings'.
|
|
frontend:
backend/src/entities/application-settings.ts#L39
Property 'confirmSpotUntil' has no initializer and is not definitely assigned in the constructor.
|
|
frontend:
backend/src/entities/application-settings.ts#L37
Property 'acceptanceDeadline' has no initializer and is not definitely assigned in the constructor.
|
|
frontend:
backend/src/entities/application-settings.ts#L35
Property 'fillProfileFormTo' has no initializer and is not definitely assigned in the constructor.
|
|
frontend:
backend/src/entities/application-settings.ts#L33
Property 'fillProfileFormFrom' has no initializer and is not definitely assigned in the constructor.
|
|
frontend:
backend/src/controllers/dto.ts#L159
Class 'SettingsDTO' incorrectly implements interface 'DTO<Omit<Settings, "updatedAt">>'.
|
|
frontend:
backend/src/controllers/dto.ts#L96
Cannot find name 'ProjectSettings'. Did you mean 'ProjectSettingsDTO'?
|
|
frontend:
backend/src/controllers/dto.ts#L74
Class 'ApplicationSettingsDTO' incorrectly implements interface 'DTO<ApplicationSettings>'.
|
|
frontend
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
style
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
backend
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|