-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Should ChatInitSettings options have a exported interface #855
Comments
@bingenito good spot - I believe this portion of the schema is incorrectly defined: FDC3/src/context/schemas/chatInitSettings.schema.json Lines 19 to 25 in dc42f96
The schema should be closer to this: {
"$schema": "http://json-schema.org/draft-07/schema#",
"$id": "https://fdc3.finos.org/schemas/next/chatInitSettings.schema.json",
"type": "object",
"title": "ChatInitSettings",
"properties": {
"type": {
"const": "fdc3.chat.initSettings"
},
"chatName": {
"type": "string"
},
"members": {
"$ref": "contactList.schema.json#"
},
"initMessage": {
"type": "string"
},
"options": {
"type": "object",
"properties": {
"groupRecipients": {"type": "boolean"},
"public": {"type": "boolean"},
"allowHistoryBrowsing": {"type": "boolean"},
"allowMessageCopy": {"type": "boolean"},
"allowAddUser": {"type": "boolean"}
}
}
},
"required": [
"type"
]
} Which does generate the properties. However, I also note that we have field with the name @mistryvinay could the Symphony team look at fixing these two issues? |
Question Area
[x] Context Data
Question
The documentation for fdc3.chatinitsettings has 5 documented optional boolean properties but the exported interface for ChatInitSettings defines options as any. Should we add the documented properties to an exported type and change options to be that type vs any?
The text was updated successfully, but these errors were encountered: