Gastón Fournier 3d9f31f839 feat: ensure at least one owner on remove user/group access (#5085) ... ## About the changes This makes sure that projects have at least one owner, either a group or a user. This is to prevent accidentally losing access to a project. We check this when removing a user/group or when changing the role of a user/group **Note**: We can still leave a group empty as the only owner of the project, but that's okay because we can still add more users to the group		2023-10-19 14:14:59 +02:00
..
access	refactor: prefer eventService.storeEvent methods (#4830)	2023-09-27 14:23:05 +01:00
change-request-access-service	feat: protect segment operations for change requests (#4417)	2023-08-04 12:23:19 +02:00
client-feature-toggles	refactor: add tests for /api/client/features (#5057)	2023-10-16 16:18:41 +02:00
dependent-features	feat: detect grandchild dependency (#5094)	2023-10-19 13:14:32 +02:00
export-import-toggles	fix: add sort to deep diff (#5084)	2023-10-18 16:34:42 +02:00
feature-naming-pattern	refactor: remove check for feature naming data object (#4745)	2023-09-15 12:51:47 +02:00
feature-toggle	fix: add project filter to feature-toggle-list-builder (#5099)	2023-10-19 15:05:56 +03:00
group	refactor: prefer eventService.storeEvent methods (#4830)	2023-09-27 14:23:05 +01:00
instance-stats	Refactor/move features to feature oriented architecture (#4994)	2023-10-11 09:38:57 +02:00
playground	fix: add project filter to feature-toggle-list-builder (#5099)	2023-10-19 15:05:56 +03:00
private-project	feat: biome lint (#4853)	2023-09-29 14:18:21 +02:00
project	feat: ensure at least one owner on remove user/group access (#5085)	2023-10-19 14:14:59 +02:00
segment	Refactor/move features to feature oriented architecture (#4994)	2023-10-11 09:38:57 +02:00
index.ts	feat: allow to delete dependencies when no orphans (#4952)	2023-10-06 13:39:16 +02:00