MultiTenant application development improvement #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lver. What it does is it takes the tenant id from query string parameter (tid by default). This allows for easier testing in development environment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, I've been playing around with the multi-tenant-core plugin and found out that there could be one addition to it that'd make familiarizing one with the idea of multitenancy a lot easier: specifying tenant id as query string parameter.
The changes that I've made do exactly that. The value of "tid" query string parameter is returned as the current tenant id.
Granted this solution is not perfect and (for example) does not work with scaffolding but it is great for educational purposes (especially while doing live presentations).