Samuel Štancl b320f8f33d Add TenantConfigBootstrapper, deprecate Feature implementation ... The feature was pretty much a soft-bootstrapper -- it listened to both Bootstrapped and Reverted. Bootstrappers have a few more protections in terms of error handling and safe reverting, so there's no point in (badly) re-implementing bootstrapper functionality within TenantConfig just so it could be a Feature. Going forward, all Features should be things that are mostly agnostic of the tenant state, and especially they should not use bootstrapped/ reverted events. Bootstrappers are simply more appropriate and safe.		2025-09-26 13:49:15 +02:00
..
impersonation-migrations	Add remember column to to the impersonation token (#1101)	2023-04-13 02:05:26 +02:00
migrations	Postgres RLS + permission controlled database managers (#33)	2024-04-24 22:32:49 +02:00
resource-syncing-migrations	Use polymorphic table for mapping resources to tenants (#997)	2023-02-02 06:39:35 +01:00
config.php	Add TenantConfigBootstrapper, deprecate Feature implementation	2025-09-26 13:49:15 +02:00
routes.php	Refactor early identification (#47)	2024-04-22 11:30:58 +02:00
TenancyServiceProvider.stub.php	resolve minor todos	2025-08-18 15:05:17 +02:00
tenant_routes.stub.php	add line end to sample route response	2024-07-09 00:15:37 +02:00