nyastodon/config
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
..
environments Merge branch 'main' into glitch-soc/merge-upstream 2022-11-17 12:01:37 +01:00
initializers Merge branch 'main' into glitch-soc/merge-upstream 2022-11-28 11:33:34 +01:00
locales make number of visible reactions a vanilla setting 2022-12-09 23:04:13 +01:00
locales-glitch initial translation of Glitch-specific texts into Czech (#1997) 2022-12-08 10:38:52 +01:00
webpack Merge branch 'main' into glitch-soc/merge-upstream 2022-08-28 11:31:00 +02:00
application.rb enable be locale (#22022) 2022-12-07 00:00:56 +01:00
boot.rb
brakeman.ignore
database.yml Change postgres connection timeout (#21790) 2022-12-07 00:39:36 +01:00
deploy.rb Change master branch to main branch (#20290) 2022-11-10 04:02:05 +01:00
environment.rb
i18n-tasks.yml Revert "Revert "Change "Allow trends without prior review" setting to include statuses (#17977)"" 2022-11-12 10:17:22 +01:00
navigation.rb Merge branch 'main' into glitch-soc/merge-upstream 2022-11-17 12:01:37 +01:00
pghero.yml
puma.rb
roles.yml
routes.rb change reaction api to match other interactions 2022-12-09 23:08:42 +01:00
secrets.yml
settings.yml make number of visible reactions a vanilla setting 2022-12-09 23:04:13 +01:00
sidekiq.yml Change incoming activity processing to happen in ingress queue (#20264) 2022-11-10 14:21:51 +01:00
storage.yml
webpacker.yml