fix issue 343 Fixed: When multiple tenants have the same cache key, tenants cannot be distinguished #344
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.
Fixed #343 : When multiple tenants have the same cache key, tenants cannot be distinguished
There will be a problem with this method: because tenants are typically handled in the middleware, if a setting class is used in the boot method of serviceProvider, the correct tenant cannot be obtained
eg:
Settings cacheKey method
You will receive a cached key:
laravel_cache_{prefix}.settings.App\Settings\{Your settings name}_team_1