Skip to content
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

defaultGroupCapability property requires lower case vs camelCase as documented (groupchat vs groupChat) #188

Open
nirvanatikku opened this issue Mar 11, 2024 · 0 comments

Comments

@nirvanatikku
Copy link

nirvanatikku commented Mar 11, 2024

Error observed when uploading: defaultGroupCapability.groupChat | Property "groupChat" has not been defined and the schema does not allow additional properties.

Issue: note the schema uses groupchat, and docs have it camel cased: https://learn.microsoft.com/en-us/microsoftteams/platform/resources/schema/manifest-schema

It appears this is in the 1.16 schema, too. Looking through the schema, a user can provide groupchat OR groupChat and it will resolve in most cases. However, in the case of the specific property defaultGroupCapability, it does not.

@nirvanatikku nirvanatikku changed the title DevPreview defaultGroupCapability property typo for groupchat (vs groupChat) 1.16+DevPreview defaultGroupCapability property typo for groupchat (vs groupChat) Mar 11, 2024
@nirvanatikku nirvanatikku changed the title 1.16+DevPreview defaultGroupCapability property typo for groupchat (vs groupChat) defaultGroupCapability property requires lower case vs camelCase as documented (groupchat vs groupChat) Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant