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

WIP: Add reactions to messages #707

Closed

Conversation

kaustubh-nair
Copy link
Member

No description provided.

@zulipbot zulipbot added the size: XL [Automatic label added by zulipbot] label Jul 3, 2020
@kaustubh-nair kaustubh-nair force-pushed the add-reactions-to-messages branch 3 times, most recently from a01b829 to fbcc1c7 Compare July 4, 2020 20:25
@kaustubh-nair kaustubh-nair marked this pull request as draft July 9, 2020 15:58
Presently, the emoji code and type for 'thumbs-up' is hard-coded
in the react_to_message method. This commit uses the stored emoji
data(in emoji_names.py) to look-up the emoji code.

This change makes it easier to use model.react_to_message, in the
future, for emojis other than the currently supported 'thumbs-up'.
A new pop-up EmojiPickerView will be triggered on pressing `:` key on a
message. This view will be used to search and select the emoji that a
user wants to add to a message.

This commit includes a minimal view that only includes the 'thumbs-up'
emoji. Buttons for this emoji, and a search bar for more emojis will be
added in subsequent commits.

Tests added.
Change the 'thumbs-up' emoji in EmojiPickerView from text to a button
which on pressing can toggle the reaction on current message.
Instead of 'thumbs-up', the user can add the first 10 reactions from
EMOJI_NAMES. A search box will be added subsequently to support adding
other reactions. This includes '+1', al alternative to 'thumbs-up' so this
commit should not cause any reduction in available features available to
the user.
This ensures there is no scrolling if the pop-up contains an edit box.
@kaustubh-nair kaustubh-nair marked this pull request as ready for review October 21, 2020 08:01
@neiljp
Copy link
Collaborator

neiljp commented Jan 24, 2021

@kaustubh-nair This was towards fixing #559? Was this blocked on something, or lost track of towards the end of GSoC?

@neiljp neiljp added this to the Next Release milestone Jan 24, 2021
@kaustubh-nair
Copy link
Member Author

@neiljp This was blocked because of PopUpView refactor, but still according to the current design it is not yet compatible with it. It requires some refactoring of Popupview for it to work properly.

@neiljp neiljp modified the milestones: 0.6.0, Release after next Jan 28, 2021
Base automatically changed from master to main January 30, 2021 20:30
@zulipbot
Copy link
Member

Heads up @kaustubh-nair, we just merged some commits that conflict with the changes your made in this pull request! You can review this repository's recent commits to see where the conflicts occur. Please rebase your feature branch against the upstream/main branch and resolve your pull request's merge conflicts accordingly.

@neiljp
Copy link
Collaborator

neiljp commented Aug 17, 2021

This work was extended into #913, fixing #559, so closing this now 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has conflicts size: XL [Automatic label added by zulipbot]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants