From c819780a689e4ae410a6d64ffd6ed84f4870ff37 Mon Sep 17 00:00:00 2001 From: Casey Dwyer Date: Thu, 26 Jan 2023 22:17:28 -0600 Subject: [PATCH] fixes confusing typo on Tenants page (#236) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * fixed typo Don't know what exactly this line is referring to (eg, `CentralConnection` concern, the `$tenant->run...` function, or something else)...but I'm 95% sure this was a typo in one direction or the other. Hope that helps! * Update tenants.blade.md Co-authored-by: Samuel Štancl --- source/docs/v3/tenants.blade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/docs/v3/tenants.blade.md b/source/docs/v3/tenants.blade.md index 66b9af0..6985d1c 100644 --- a/source/docs/v3/tenants.blade.md +++ b/source/docs/v3/tenants.blade.md @@ -12,7 +12,7 @@ The package comes with a base `Tenant` model that's ready for common things, tho The base model has the following features on top of the ones that are necessary by the interface: -- Forced central connection (lets you interact with Tenant models even in tenant contexts) +- Forced central connection (lets you interact with `Tenant` models even in the tenant context) - Data column trait — lets you store arbitrary keys. Attributes that don't exist as columns on your `tenants` table go to the `data` column as serialized JSON. - Id generation trait — when you don't supply an ID, a random uuid will be generated. An alternative to this would be using AUTOINCREMENT columns. If you wish to use numerical ids, change the `create_tenants_table` migration to use `bigIncrements()` or some such column type, and set `tenancy.id_generator` config to null. That will disable the ID generation altogether, falling back to the database's autoincrement mechanism.