@nrwl/tao fails to validate schema in case of multiple types

I’m using “@nrwl/angular”: “^12.9.0” and “@angular/fire”: “~7.2.0”.

@angular/fire:deploy accepts the following parameter in its schema:

{
  "$schema": "http://json-schema.org/draft-07/schema",
  "$id": "FirebaseDeploySchema",
  "title": "Firebase Deploy",
  "description": "Ng Deploy target options for Firebase.",
  "properties": {
    // ...
    "ssr": {
      "type": ["boolean", "string"],
      "description": "Should we attempt to deploy the function to Cloud Functions (true or 'cloud-functions') / Cloud Run ('cloud-run') or just Hosting (false)"
    }
  }
}

In my angular.json I have:

"deploy": {
	"builder": "@angular/fire:deploy",
	"options": {
		"prerender": false,
		"ssr": false,
		"browserTarget": "my-app:build:production",
		"firebaseProject": "my-project-id",
	}
}

Current Behavior

If I run: nx run my-app:deploy, it fails:

Property 'ssr' does not match the schema. 'false' should be a 'boolean,string'.

Expected Behavior

It runs successfully. I don’t know if it’s ever worked.

Considerations

I’m pretty sure it depends on validation logic, that does not take into account the possibility of (valid) mutliple types in the schema.

[fr-esco]

Is there anything I could add?

[fr-esco]

Actually, I’m referring to multiple types, as per the last example of this page: https://json-schema.org/understanding-json-schema/reference/type.html

{ "type": ["number", "string"] }

The definition of type is:

The type keyword may either be a string or an array:

• If it’s a string, it is the name of one of the basic types above.
• If it is an array, it must be an array of strings, where each string is the name of one of the basic types, and each element is unique. In this case, the JSON snippet is valid if it matches any of the given types.