You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These direct queries bypass any logic that might exist when it comes to types. The default tagging library doesn't do much in the scope, but any library based on that one loses its extra functionality.
Was there a reason to avoid to the scope? Would you take a PR that swapped the queries to use the scope?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
There are a few places in the codebase where the
typecolumn is queried directly instead of using the availablewithTypescope.typebeing queried directly: https://github.com/search?q=repo%3Aspatie%2Fnova-tags-field%20%22where(%27type%22&type=codewithTypescope: https://github.com/spatie/laravel-tags/blob/main/src/Tag.php#L31These direct queries bypass any logic that might exist when it comes to types. The default tagging library doesn't do much in the scope, but any library based on that one loses its extra functionality.
Was there a reason to avoid to the scope? Would you take a PR that swapped the queries to use the scope?
Beta Was this translation helpful? Give feedback.
All reactions