Incorrect type-cast for boolean config values

[the-other-dev]

Describe the Bug

For config options there is an automatic type-casting (https://docs.directus.io/self-hosted/config-options.html#type-casting-and-nesting). In the code, the relevant parts are in the env package lib/cast.ts and utils/guess-type.ts.

When using an actual boolean value in the config options, the parsed value turns into 0 instead of false or 1 instead of true.

I believe that this issue is there since version v10.9.0 when the env package was introduced.

To Reproduce

Add an option with the type boolean to the config.json, e.g. "MY_VARIABLE": false.
Retrieve the parsed value via:

const env = useEnv();
console.log(env['MY_VARIABLE']); // Prints 0 instead of false

The current work-around is to define the option as a string "MY_VARIABLE": "false" (returns false in the application).

Also, here are two test cases for guess-type.test.ts that currently fail due to the issue:

test('Returns boolean if value is boolean true', () => {
    expect(guessType(true)).toBe('boolean'); // Fails because it returns "number" currently
});

test('Returns boolean if value is boolean false', () => {
    expect(guessType(false)).toBe('boolean'); // Fails because it returns "number" currently
});

Directus Version

v10.10.7

Hosting Strategy

Self-Hosted (Docker Image)

[hanneskuettner]

Heya! Thank you for opening this issue, as it turns out, this looks like a duplicate of #21744. I'll proceed to close this issue. You can follow along in #21744 for the progress.

[the-other-dev]

Thanks! My bad, I did not see that one!