Open LiamAird opened 3 years ago
Hi @LiamAird, thank you for submitting a new issue with all the relevant details. I will see if there is something that can be done to help with this, but unfortunately so far it has been very difficult for multiple packages that change the behavior of newEloquentBuilder
to co-exist.
It seems that the general written work-around is to create a new trait, that implements this newEloquentBuilder trait - so that it is namespaced differently and therefore will not collide.
In my opinion this is not something that the general user should do, to make packages work - so if you can find a way to make it work, I'd be forever grateful! :) If not, we will have to find a way to make a trait ourselves and have it written up in the guides as a "work-around" fix to use this package with others, that utilizes the same methods.
@LiamAird I may have a solution for this, working on it now.
@LiamAird Could you give release 0.10.2 a try and let me know if that fixes the issue? Please see the readme section towards the top regarding conflicting packages as how to implement it. Thanks!
@mikebronner Any progress on this, since the latest change did not work as expected. Also seems like the latest conversation got deleted.
@LiamAird I am still working toward a full solution. I noticed after publishing 0.10.2 that it wasn't working as expected, and will hopefully have a solution in the near future.
Any information on this? It's also blocking me to upgrade for some time.
@C10ne Can you install 0.10.1 in the meantime?
Is there any update on this? I am still having the collision issue on version 0.11.1
@mefenlon Hi, sorry, I have not been able to get to working on a solution for this yet due to a very chaotic past several months on my end.
Mike, Thank you for taking the time to reply. I hear you and hope the chaos subsides in the near future.
On Mon, Feb 8, 2021 at 1:37 PM Mike Bronner notifications@github.com wrote:
@mefenlon https://github.com/mefenlon Hi, sorry, I have not been able to get to working on a solution for this yet to to a very chaotic past several months on my end.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/GeneaLabs/laravel-model-caching/issues/366#issuecomment-775355612, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHKI47KQYKXZEMJ6UKH5RD3S6AVN5ANCNFSM4QSTAOFQ .
Hey, any update on this? We would also like to use both traits parallel :)
Describe the bug When using this package, together with other packages, that also use the newEloquentBuilder, it will fail, since two cannot use the same method two redo the eloquentBuilder, I suppose.
Eloquent Query Please provide the complete eloquent query that caused the bug, for example:
Using the NodeTrait from Kalnoy, as mentioned above.
Stack Trace The full stack trace from your log file.
Environment
Additional context
This seems to be a general issue, when using these packages, that uses the same general commands. Presented in this issue: #137 https://github.com/lazychaser/laravel-nestedset/issues/360