Skip to content

Some schemas erroneously pass strict validation checks #5991

Description

@Vessel9817

Area with issue?

Build server

✔️ Expected Behavior

If a schema isn't included in ajvNotStrictMode, it should be subject to strict validation in its entirety. That means that the use of type unions in schemas should result in strict validation failing with the following error message:

Error: strict mode: use allowUnionTypes to allow union type keyword at "..." (strictTypes)

❌ Actual Behavior

Strict validation passes in exceptional circumstances.

JSON, YAML, or TOML file that does not work.

The current revision of host-meta.json, whose issues have since been fixed in #5990. Other such cases exist.

IDE or code editor.

None

Are you making a PR for this?

No, someone else must create the PR.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions