Andrea Maria Piana c38ec00a2d Add community request to response when a response handled ...

In general, any time a piece of state is updated in the backend, that
should be propagated to the client through signals.

In this case, when a request was accepted, the client wasn't notified,
requiring them to re-fetch the accepted requests and causing
inconsistent state between status-go and client.

2023-02-07 13:17:19 +00:00

..

migrations

Handle organisation membership requests

2020-12-23 17:20:55 +01:00

adaptors.go

feat: sync CommunitySettings across paired devices

2022-06-16 12:45:05 +02:00

community_categories_test.go

Validate no duplicated community chat names

2021-06-03 13:27:49 +02:00

community_categories.go

Upgrade linter to 1.50.0

2023-01-13 17:52:03 +00:00

community_test.go

fix: remove ourselves from members when leaving community

2022-09-21 08:35:52 +02:00

community.go

Upgrade linter to 1.50.0

2023-01-13 17:52:03 +00:00

errors.go

Allow owner/admin to delete messages of a community (#2958)

2022-12-02 19:34:02 +08:00

manager_test.go

refactor(import-tool): process import data in chunks

2023-01-30 12:23:56 +01:00

manager.go

Add community request to response when a response handled

2023-02-07 13:17:19 +00:00

persistence_test_helpers.go

feat: add SpectateCommunity api

2022-10-06 21:21:37 +02:00

persistence_test.go

feat: add SpectateCommunity api

2022-10-06 21:21:37 +02:00

persistence.go

Add community request to response when a response handled

2023-02-07 13:17:19 +00:00

request_to_join_test.go

Sync Communities (#2253)

2021-08-06 16:40:23 +01:00

request_to_join.go

feat(communities): Cancel request to join community (#2915)

2022-10-28 11:41:20 +03:00

request_to_leave.go

feat: introduce and distribute RequestToLeave community

2022-08-26 11:25:33 +02:00

utils.go

feat: introduce and distribute RequestToLeave community

2022-08-26 11:25:33 +02:00

validator.go

feat: community tags (#2708)

2022-06-24 09:40:12 -04:00