fef e3f97f60a6 change reaction api to match other interactions ... Status reactions had an API similar to that of announcement reactions, using PUT and DELETE at a single endpoint. I believe that for statuses, it makes more sense to follow the convention of the other interactions and use separate POST endpoints for create and destroy respectively.		2022-12-09 23:08:42 +01:00
..
chewy	Change algorithm of tootctl search deploy to improve performance (#18463)	2022-05-22 22:16:43 +02:00
controllers	change reaction api to match other interactions	2022-12-09 23:08:42 +01:00
helpers	Merge branch 'main' into glitch-soc/merge-upstream	2022-11-12 13:28:03 +01:00
javascript	change reaction api to match other interactions	2022-12-09 23:08:42 +01:00
lib	make number of visible reactions a vanilla setting	2022-12-09 23:04:13 +01:00
mailers	Add support for language preferences for trending statuses and links (#18288)	2022-10-08 16:45:40 +02:00
models	make number of visible reactions a vanilla setting	2022-12-09 23:04:13 +01:00
policies	Merge branch 'main' into glitch-soc/merge-upstream	2022-11-17 12:01:37 +01:00
presenters	Change sign-in banner to reflect disabled or moved account status (#19773)	2022-11-05 18:28:13 +01:00
serializers	make number of visible reactions a vanilla setting	2022-12-09 23:04:13 +01:00
services	fix reaction deletion bug and clean up controller	2022-12-09 23:08:42 +01:00
validators	change default reaction limit to 1	2022-12-09 23:04:13 +01:00
views	make number of visible reactions a vanilla setting	2022-12-09 23:04:13 +01:00
workers	Merge branch 'main' into glitch-soc/merge-upstream	2022-11-12 13:28:03 +01:00