feat!: synchronize (most) features with frontend-build and frontend-platform #46
Annotations
10 errors
|
runtime/analytics/SegmentAnalyticsService.js#L30
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
|
|
runtime/auth/AxiosCsrfTokenService.js#L37
Prefer using nullish coalescing operator (`??=`) instead of an assignment expression, as it is simpler to read
|
|
runtime/auth/AxiosJwtAuthService.js#L226
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
|
|
runtime/auth/AxiosJwtAuthService.js#L233
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
|
|
runtime/auth/AxiosJwtAuthService.js#L337
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
|
|
runtime/config/index.ts#L284
Prefer using nullish coalescing operator (`??=`) instead of an assignment expression, as it is simpler to read
|
|
runtime/initialize.js#L332
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
|
|
runtime/initialize.js#L333
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
|
|
runtime/initialize.js#L334
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
|
|
runtime/logging/NewRelicLoggingService.js#L138
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
|
The logs for this run have expired and are no longer available.
Loading