use
Boolean(process.env.CI) instead20 AUTH_SECRET: process.env.AUTH_SECRET,
21 AUTH_URL: process.env.AUTH_URL,
22 },
23 skipValidation: !!process.env.CI || !!process.env.SKIP_ENV_VALIDATION,24});
use
Boolean(process.env.SKIP_ENV_VALIDATION) instead20 AUTH_SECRET: process.env.AUTH_SECRET,
21 AUTH_URL: process.env.AUTH_URL,
22 },
23 skipValidation: !!process.env.CI || !!process.env.SKIP_ENV_VALIDATION,24});
use
Boolean(secret.value) instead165 const secretKinds = getSecretKinds(input.kind);
166 const secrets = input.secrets.filter(
167 (secret): secret is { kind: IntegrationSecretKind; value: string } =>
168 !!secret.value,169 );
170 const everyInputSecretDefined = secretKinds.every((secretKind) =>
171 secrets.some((secret) => secret.kind === secretKind),use
Boolean(process.env.SKIP_ENV_VALIDATION) instead34 },
35 skipValidation:
36 !!process.env.CI ||
37 !!process.env.SKIP_ENV_VALIDATION ||38 process.env.npm_lifecycle_event === "lint",
39});
use
Boolean(process.env.CI) instead33 // NEXT_PUBLIC_CLIENTVAR: process.env.NEXT_PUBLIC_CLIENTVAR,
34 },
35 skipValidation:
36 !!process.env.CI ||37 !!process.env.SKIP_ENV_VALIDATION ||
38 process.env.npm_lifecycle_event === "lint",
39});
Description
Prefer using explicit casts by calling Number, Boolean, or String over using operators like +, !! or "" +.
This is considered best practice as it improves readability.
Bad Practice
const b = !!foo;
// The `+` operator does not change the value of its operand
// unless it's already a number.
let n = +foo;
n = 1 * foo;
const s = "" + foo;
Recommended
const b = Boolean(foo);
const n = Number(foo);
const s = String(foo);