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
The practic of extending builder through newEloquentBuilder is becoming more and more common.
Package owners and project devs - everybody wants to use their own builders.
But since this package uses full custom QueryBuilder class, it is hard to combine with other custom builders.
If we had all builder logic inside a trait instead, this would save the day.
It sound like not hard to do - neither does it ruin backward compatibility - unless I'm missing something.
There was this old request showing how it can be done (but it is stale now): #229
The text was updated successfully, but these errors were encountered:
Hi!
The practic of extending builder through newEloquentBuilder is becoming more and more common.
Package owners and project devs - everybody wants to use their own builders.
But since this package uses full custom QueryBuilder class, it is hard to combine with other custom builders.
If we had all builder logic inside a trait instead, this would save the day.
It sound like not hard to do - neither does it ruin backward compatibility - unless I'm missing something.
There was this old request showing how it can be done (but it is stale now):
#229
The text was updated successfully, but these errors were encountered: