Fixing wrong schema defaults for mutually exclusive fields (#19281)

* hotfix(api): Updated create tag schema's mutually exclusive field

* hotfix(api): Updated create tag schema's mutually exclusive field

---------

Co-authored-by: Mayur Singal <39544459+ulixius9@users.noreply.github.com>
This commit is contained in:
DataOps7 2025-03-18 13:20:10 +02:00 committed by GitHub
parent 2bc34d99cf
commit cb98269dea
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 2 additions and 2 deletions

View File

@ -25,7 +25,7 @@
"mutuallyExclusive" : {
"description" : "Tags under this classification are mutually exclusive. When mutually exclusive is `true` the tags from this classification are used to **classify** an entity. An entity can only be in one class - example, it can only be either `tier1` or `tier2` and not both. When mutually exclusive is `false`, the tags from this classification are used to **categorize** an entity. An entity can be in multiple categories simultaneously - example a customer can be `newCustomer` and `atRisk` simultaneously.",
"type" : "boolean",
"default" : "false"
"default" : false
},
"domain" : {
"description": "Fully qualified name of the domain the Table belongs to.",

View File

@ -43,7 +43,7 @@
"mutuallyExclusive" : {
"description" : "Children tags under this group are mutually exclusive. When mutually exclusive is `true` the tags from this group are used to **classify** an entity. An entity can only be in one class - example, it can only be either `tier1` or `tier2` and not both. When mutually exclusive is `false`, the tags from this group are used to **categorize** an entity. An entity can be in multiple categories simultaneously - example a customer can be `newCustomer` and `atRisk` simultaneously.",
"type" : "boolean",
"default" : "false"
"default" : false
},
"domain" : {
"description": "Fully qualified name of the domain the Table belongs to.",