chuckya/app
fef be710b6a5f 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.
2023-05-07 15:05:56 -07: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 2023-05-07 15:05:56 -07:00
helpers Merge branch 'main' into glitch-soc/merge-upstream 2023-04-29 10:44:56 +02:00
javascript change reaction api to match other interactions 2023-05-07 15:05:56 -07:00
lib handle misskey reactions properly 2023-05-07 15:05:56 -07:00
mailers Add user handle to notification mail recipient address (#24240) 2023-04-17 11:06:06 +02:00
models cherry-pick emoji reaction changes 2023-05-07 15:05:56 -07:00
policies Merge branch 'main' into glitch-soc/merge-upstream 2022-11-17 12:01:37 +01:00
presenters Remove unused InstancePresenter methods (#24206) 2023-03-22 14:15:22 +01:00
serializers make number of visible reactions a vanilla setting 2023-05-07 15:05:56 -07:00
services fix reaction deletion bug and clean up controller 2023-05-07 15:05:56 -07:00
validators change default reaction limit to 1 2023-05-07 15:05:56 -07:00
views make number of visible reactions a vanilla setting 2023-05-07 15:05:56 -07:00
workers Merge branch 'main' into glitch-soc/merge-upstream 2023-04-29 10:44:56 +02:00