Skip to content
This repository has been archived by the owner on Sep 11, 2024. It is now read-only.

Properly disable composer access when recording a voice message #5870

Merged
merged 3 commits into from
Apr 16, 2021

Conversation

turt2live
Copy link
Member

@turt2live turt2live commented Apr 14, 2021

This PR splits recording management out to a store instead of using callbacks through the components, given more and more components will want to watch for voice recording updates. This then re-routes the disabled flag through to the composer to properly disable itself.

The composer text entry otherwise looks exactly the same when disabled versus not. We prevent all efforts we can to have people accidentally end up in the composer, but don't stop them if they somehow get in there - there's not much value to making absolutely sure someone can't send a message.


Reviewer: This is reviewable commit-by-commit (recommended)


Screenshot which looks eerily like the existing setup:
image

@turt2live turt2live force-pushed the travis/voice/disable-composer branch from 6359caa to fedb5b9 Compare April 15, 2021 02:12
@turt2live turt2live requested a review from a team April 15, 2021 02:18
Copy link
Member

@dbkr dbkr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Store looks like a big improvement 👍

@turt2live turt2live merged commit 7878e1c into develop Apr 16, 2021
@turt2live turt2live deleted the travis/voice/disable-composer branch April 16, 2021 13:36
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants