Closed keithbrink closed 1 year ago
Any reason you did no start with #520 ?? We were close on that PR and just a few tweaks requested, was goin to pick it up myself later in the month to finish off
@dpslwk Didn't see it! I'll have a look at it now.
Working on converting the caches over, marked as draft for now.
MasterSlaveConnection
was not remove so much as changed to PrimaryReadReplicaConnection
we had a request to make the same changes https://github.com/laravel-doctrine/orm/pull/520#discussion_r973195088 in #520
MasterSlaveConnection
was not remove so much as changed toPrimaryReadReplicaConnection
we had a request to make the same changes #520 (comment) in #520
Yeah, to be more precise, the new PrimaryReadReplica was already supported in Laravel Doctrine, but it also supported the old MasterSlaveConnection for backwards compatibility. This has now been completely removed from DBAL 3: https://github.com/doctrine/dbal/blob/3.5.x/UPGRADE.md#removed-masterslaveconnection
Base: 53.56% // Head: 57.94% // Increases project coverage by +4.37%
:tada:
Coverage data is based on head (
ff3ea4c
) compared to base (d2c8bc0
). Patch coverage: 78.78% of modified lines in pull request are covered.
:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Using this branch within my application and all seems to be good - ready for review.
Could you add an UPGRADE.md
with notes on moving to 2.x version of laravel-doctrine/orm
Could you add an
UPGRADE.md
with notes on moving to 2.x version oflaravel-doctrine/orm
Done.
Did some research into the namespaces
thing.
MappingDriverChain
with a default driverLaravelDoctrine
Permission
entity). It calls the MappingDriverChain::addPaths()
.^1
works by reusing the same driver for each namespaceBasically the namespace support doesn't seem to have any effect at all. The entities doesn't need to be in any of the namespaces.
@keithbrink I merged 1.7 into 1.8 and noticed the cs-fixer things was already handled there. Sorry about that 🤦🏻♂️
@eigan No problem, I rebased on 1.8.
@keithbrink Thank you! This is a good starting point for 2.0. Going to update the other laravel-doctrine packages to allow this version soon. Will try to get this out to our staging env tomorrow, then production next friday.
@eigan Thanks for getting this across the finish line!
Following on the work of #519 and #520, I went through the code to fix all the breaking changes related to DBAL 3, as well as some deprecations that came up.
I would prefer to target a new 2.0 branch with this, since there are many breaking changes.
json_array
type has been removed in DBAL 3.create
method on the EntityManager: https://github.com/doctrine/orm/pull/9961