-
Notifications
You must be signed in to change notification settings - Fork 57
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
[MM-61166] Ensure full validation of Calls post props #885
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
webapp/src/utils.ts
Outdated
recordings: isValidObject(post.props?.recordings) ? post.props.recordings : {}, | ||
transcriptions: isValidObject(post.props?.transcriptions) ? post.props.transcriptions : {}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to validate that the recordings and transcriptions objects are valid?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cpoile They are not used right now, but we should. Let me tackle that as part of https://mattermost.atlassian.net/browse/MM-61228
* Surface transcriptions in call post * Add proper job metadata validation
* Ensure full validation of Calls post props * [MM-61228] Surface transcriptions in call post (#886) * Surface transcriptions in call post * Add proper job metadata validation
* Ensure full validation of Calls post props * [MM-61228] Surface transcriptions in call post (#886) * Surface transcriptions in call post * Add proper job metadata validation
* [MM-61166] Ensure full validation of Calls post props (#885) * Ensure full validation of Calls post props * [MM-61228] Surface transcriptions in call post (#886) * Surface transcriptions in call post * Add proper job metadata validation * [MM-61298] Fix e2e pipeline (#888) * Fix e2e pipeline * We don't need ES * Fix docker login step (#881) * Fix docker login step * Update .github/workflows/e2e.yml Co-authored-by: Mario Vitale <mvitale1989@hotmail.com> --------- Co-authored-by: Mario Vitale <mvitale1989@hotmail.com> * Fix e2e pipeline flakyness (#867) --------- Co-authored-by: Mario Vitale <mvitale1989@hotmail.com>
* [MM-61298] Fix e2e pipeline (#888) * Fix e2e pipeline * We don't need ES * Fix docker login step (#881) * Fix docker login step * Update .github/workflows/e2e.yml Co-authored-by: Mario Vitale <mvitale1989@hotmail.com> --------- Co-authored-by: Mario Vitale <mvitale1989@hotmail.com> * [MM-61166] Ensure full validation of Calls post props (#885) * Ensure full validation of Calls post props * [MM-61228] Surface transcriptions in call post (#886) * Surface transcriptions in call post * Add proper job metadata validation --------- Co-authored-by: Mario Vitale <mvitale1989@hotmail.com>
Summary
Since props cannot be trusted (i.e., users can alter them at any time on their posts), we must take extra care to ensure that the type of them is what we expect it to be.
Ticket Link
https://mattermost.atlassian.net/browse/MM-61166