I've clarified how the data column works along with how to update a tenant's custom column and an attribute in its data column. I've also cleared up how the getCustomColumns() function works (When I first used the package I thought it meant to define columns that will be used in the data column).
* Update passport.blade.md
Added a note about using Passport in the Central and client applications.
* Update source/docs/v3/integrations/passport.blade.md
Co-authored-by: Samuel Štancl <samuel.stancl@gmail.com>
* chore: (Improve documentation search for V3)
* fix: checks for mispelled words
* fix: mispelled words
* fix spaces and syntax
* Update multi-database-tenancy.blade.md
Co-authored-by: Samuel Stancl <samuel.stancl@gmail.com>
* Update testing.blade.md
Added call to parent's setUp() method others some essential operations will not be run e.g resetting of db, etc.
* Reindent
Co-authored-by: Samuel Stancl <samuel.stancl@gmail.com>
- Fixed the snippet for passing tags to the job
- Wrapped content in a Tags header to prepare for more content in the
future
- Added comment to method to mimic Laravel's documentation regardin the
matter
- Made it slightly more clear that the tags method should be applied to
the actual job class
I believe this paragraph has the information switched. A string in the `domain` column that contains a **dot** would represent a domain/hostname and a string in this column without a dot, would represent a subdomain. The current documentation has this flipped.
It had me second guessing myself. Unless I am misunderstanding something.
Maybe I am misunderstanding things, and if so, then disregard this PR.
