pleroma-fe/src
Ilja 4587f37dd7 Allow canceling a follow request
When a follow request is sent, but not (yet) accepted, the behaviour is now to cancel the request instead of re sending.

The reason is double
* You couldn't cancel a follow request if you change your mind and the request wasn't answered yet
* Instances don't always correctly process a new follow request when the following is already happening. If something went wrong (e;g. the target server thinks you're following, but your instance thinks you're not yet), it's better to first sent an unfollow. This is the behaviour that Mastodon and most probably most other clients have. Therefore this flow is more tested and expected by other instances.
2021-12-12 18:09:21 +01:00
..
assets Use an existing image served by backend instead 2019-02-03 13:30:54 -05:00
boot Use old value to discover if Shoutbox is available until we ship a new release that's declaring the feature as "shout" 2021-06-01 16:48:40 -05:00
components Allow canceling a follow request 2021-12-12 18:09:21 +01:00
directives refactor using Set 2019-10-21 20:57:36 -04:00
hocs make with-load-more not use computeds when they don't work for it 2020-12-28 17:08:15 +02:00
i18n Allow canceling a follow request 2021-12-12 18:09:21 +01:00
lib Linting + docs 2020-06-13 11:53:16 +02:00
modules Merge branch 'showMobileNewPost' into 'develop' 2021-09-09 12:19:53 +00:00
services entity_normalizer: Escape name when parsing user 2021-11-16 20:35:23 +03:00
_variables.scss Add Chats 2020-07-08 15:21:31 +03:00
App.js Merge branch 'develop' into 'showMobileNewPost' 2021-06-15 21:49:33 +00:00
App.scss moved transparent button styles into button itself 2021-06-08 10:14:49 +03:00
App.vue Merge branch 'develop' into 'showMobileNewPost' 2021-06-15 21:49:33 +00:00
main.js Rename legacy PleromaFE Chat functionality to "Shout" 2021-06-01 12:51:20 -05:00
sw.js ServiceWorker: Use clearer variable names 2020-06-19 15:24:06 +02:00