Skip to content

Refine functionality and behaviour for sub-tenancies #106

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
3 tasks
ollieread opened this issue Feb 19, 2025 · 0 comments
Open
3 tasks

Refine functionality and behaviour for sub-tenancies #106

ollieread opened this issue Feb 19, 2025 · 0 comments
Assignees
@ollieread
Labels
status: investigating The issue is being investigated status: planning The issue is being planned for the future type: refactor Refactoring of code

Comments

@ollieread
Copy link
Member

ollieread commented Feb 19, 2025 •
edited
Loading

It's currently possible to have multiple tenancies within an application, but the behaviour of both Sprout and Laravel, when layering these, is both unknown and uncertain. This needs to be looked into.

  • Introduce the ability for a tenancy to rely on another
  • Allow for multiple tenancies to be resolved for a single request
  • Allow identity resolvers to stack
@ollieread ollieread added status: investigating The issue is being investigated status: planning The issue is being planned for the future type: refactor Refactoring of code labels Feb 19, 2025
@ollieread ollieread self-assigned this Feb 19, 2025
@ollieread ollieread moved this from Ready to Backlog in Sprout Development Roadmap Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ollieread ollieread

Labels
status: investigating The issue is being investigated status: planning The issue is being planned for the future type: refactor Refactoring of code
Projects
Sprout Development Roadmap
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ollieread