fix: Fixing issue when using a different table to store pivot data #492
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.
This fixes an issue when you use a different table name to store pivot data between tags and taggables.
Let's say you use "lorem_tags" to store tags, and "lorem_tag_model" to store pivot data, and on pivot table you have "tag_id, model_id, model_type", when you set on config:
It'll look for the models table to check the pivot instead of lorem_tag_model