Change guessType to retain value types if they are known

[hanneskuettner]

Scope

If configuration parameters are read from any location, where they already have a correct type, e.g. from a .js or .yaml file this information is lost, and can actually lead to guessType guessing the wrong type, e.g. 'number' for a boolean value.

What's changed:

• Change guessType to retain the type of unknown value, if they are boolean, number or array.

Potential Risks / Drawbacks

• I don't think we explicitly allowed, e.g. DB_EXCLUDE_TABLES: ['foo', 'bar'] before, but would allow it now
• Anyone who has been abusing ANY_CONFIG_VALUE: true to equal 1 will have a problem now (let's not hope so)

Review Notes / Questions

• Does this warrant a notice in the changeset?
• Should we add test cases to cast.test.ts that cover all combinations of cast flags and values and test it without mocking all the functions in between? Right now everything is mocked out.

---

Fixes #21744

[changeset-bot]

🦋 Changeset detected

Latest commit: 0625e49

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@directus/env	Patch
@directus/api	Patch
directus	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[licitdev]

Guessing accuracy increased! 🚀