Tenants will need to be resolved for routes, this should be done by:

• [ ] Using a piece of middleware as a marker, to mark a route as requiring a tenant
  • [ ] Middleware should be aliased as tenanted
  • [ ] Middleware should also take two optional arguments, tenancy name and resolver name, i.e. tenanted:projects,subdomain
• [ ] Listening for the RouteMatched event and resolving the tenant before the controller, to make use of DI
• [ ] Optionally providing a fallback handler for when there's no route

Create an implementation of TenantResolver that uses a subdomain to identify the tenant.

The implementation will require:

• [ ] The domain the subdomains should belong to

This implementation should:

• [ ] Support the usage of a parameter named using the resolvers registered name, and the name of tenancy, i.e. project_subdomain
• [ ] Fallback to extracting the subdomain from the current host, if no parameter is present
• [ ] Implement the ActsAsMiddleware contract and set the default value of the parameter
• [ ] Register routes with the appropriate middleware and set the domain to be a parameterised subdomain of the resolvers "main domain"

Create an implementation of TenantResolver that uses the session to identify the tenant.

The implementation will require:

• An instance of Laravels Session class
• An optional name of the session

This implementation should:

• [ ] Generate a session name if none is provided, using the name it was registered under, and the name of the tenancy, i.e. project_session.
• [ ] Implement the ActsAsMiddleware contract, adding a value to the session if there's a tenant and the value isn't present
• [ ] Register routes with the appropriate middleware

Create an implementation of TenantResolver that uses the path to identify the tenant.

The implementation will require:

• An optional segment index, defaulting to 0

This implementation should:

• [ ] Support the usage of a parameter named using the resolvers registered name, and the name of tenancy, i.e. project_path
• [ ] Fallback to using the segment provided by the constructor, if no parameter is present
• [ ] Implement the ActsAsMiddleware contract and set the default value of the parameter
• [ ] Register routes with the appropriate middleware and path prefix using the parameter

Create an implementation of TenantResolver that uses a header to identify the tenant.

The implementation will require:

• An optional name for the header

This implementation should:

• [ ] Generate a header name if none is provided, using the name of the tenancy formatted as a header, i.e. Project
• [ ] Implement the ActsAsMiddleware contract, that when a Response is generated, will make sure the header is present
• [ ] Register routes with the appropriate middleware

Create an implementation of TenantResolver that uses a cookie to identify the tenant.

The implementation will require:

• An instance of Laravels CookieJar
• An optional name for the cookie

This implementation should:

• [ ] Generate a cookie name if none is provided, using the name it was registered under, and the name of the tenancy, i.e. project_cookie.
• [ ] Implement the ActsAsMiddleware contract, that when a Response is generated, will queue a cookie, if one isn't present, for the current tenant
• [ ] Register routes with the appropriate middleware