stancl/tenancy-docs
1
0
Fork 0
mirror of https://github.com/stancl/tenancy-docs.git synced 2025-12-12 02:04:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

on -> in

Browse source
This commit is contained in:
Samuel Stancl 2020-07-26 21:45:09 +02:00 • committed by GitHub
parent 2b6aa9b20e
commit 141b9fdbc2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
source/docs/v3/features/universal-routes.blade.md
View file

@ -10,7 +10,7 @@ section: content
Sometimes, you may want to use the exact same **route action** both in the central application and the tenant application. Note the emphasis on route **action** — you may use the same **path** with different actions in central & tenant routes, whereas this section covers using the same **route and action**. Sometimes, you may want to use the exact same **route action** both in the central application and the tenant application. Note the emphasis on route **action** — you may use the same **path** with different actions in central & tenant routes, whereas this section covers using the same **route and action**.
Generally, try to avoid these use cases as much as possible and prefer duplicating the code. Using the same controller and model for users in central & tenant apps will break down once you need slightly different behavior — e.g. different views returned by controllers, different behavior on models, etc. Generally, try to avoid these use cases as much as possible and prefer duplicating the code. Using the same controller and model for users in central & tenant apps will break down once you need slightly different behavior — e.g. different views returned by controllers, different behavior in models, etc.
First, enable the `UniversalRoutes` feature by uncommenting the following line in your `tenancy.features` config: First, enable the `UniversalRoutes` feature by uncommenting the following line in your `tenancy.features` config:
@ -36,4 +36,4 @@ Route::get('/foo', function () {
And the route will work in both central and tenant applications. Should a tenant be found, tenancy will be initialized. Otherwise, the central context will be used. And the route will work in both central and tenant applications. Should a tenant be found, tenancy will be initialized. Otherwise, the central context will be used.
If you're using a different middleware, look at the `UniversalRoutes` feature source code and change the public static property accordingly. If you're using a different middleware, look at the `UniversalRoutes` feature source code and change the public static property accordingly.