zulip

Commit Graph

Author	SHA1	Message	Date
rht	4975122338	zerver/migrations: Remove from __future__ import *.	2017-09-28 10:16:18 -07:00
Umair Khan	aeb68a6643	zerver: Add on_delete arg in foreign keys. on_delete will be a required arg for ForeignKey in Django 2.0. Set it to models.CASCADE on models and in existing migrations if you want to maintain the current default behavior. See https://docs.djangoproject.com/en/1.11/ref/models/fields/#django.db.models.ForeignKey.on_delete	2017-06-13 15:13:45 -07:00
Arpith Siromoney	001847ac5b	Add backend support for emoji reactions. This commit adds the following: 1. A reaction model that consists of a user, a message and an emoji that are unique together (a user cannot react to a particular message more than once with the same emoji) 2. A reaction event that looks like: { 'type': 'reaction', 'op': 'add', 'message_id': 3, 'emoji_name': 'doge', 'user': { 'user_id': 1, 'email': 'hamlet@zulip.com', 'full_name': 'King Hamlet' } } 3. A new API endpoint, /reactions, that accepts POST requests to add a reaction to a message 4. A migration to add the new model to the database 5. Tests that check that (a) Invalid requests cannot be made (b) The reaction event body contains all the info (c) The reaction event is sent to the appropriate users (d) Reacting more than once fails It is still missing important features like removing emoji and fetching them alongside messages.	2016-11-26 18:10:21 -08:00

Author

SHA1

Message

Date

rht

4975122338

zerver/migrations: Remove from __future__ import *.

2017-09-28 10:16:18 -07:00

Umair Khan

aeb68a6643

zerver: Add on_delete arg in foreign keys.

on_delete will be a required arg for ForeignKey in Django 2.0. Set it
to models.CASCADE on models and in existing migrations if you want to
maintain the current default behavior.
See https://docs.djangoproject.com/en/1.11/ref/models/fields/#django.db.models.ForeignKey.on_delete

2017-06-13 15:13:45 -07:00

Arpith Siromoney

001847ac5b

Add backend support for emoji reactions.

This commit adds the following:

1. A reaction model that consists of a user, a message and an emoji that
are unique together (a user cannot react to a particular message more
than once with the same emoji)
2. A reaction event that looks like:
    {
        'type': 'reaction',
	'op': 'add',
	'message_id': 3,
	'emoji_name': 'doge',
	'user': {
	    'user_id': 1,
            'email': 'hamlet@zulip.com',
            'full_name': 'King Hamlet'
	}
    }
3. A new API endpoint, /reactions, that accepts POST requests to add a
reaction to a message
4. A migration to add the new model to the database
5. Tests that check that
   (a) Invalid requests cannot be made
   (b) The reaction event body contains all the info
   (c) The reaction event is sent to the appropriate users
   (d) Reacting more than once fails

It is still missing important features like removing emoji and
fetching them alongside messages.

2016-11-26 18:10:21 -08:00

3 Commits