Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace phpro/zf-doctrine-hydration-module with doctrine/doctrine-laminas-hydrator #34

Open
wants to merge 5 commits into
base: 2.5.x
Choose a base branch
from

Conversation

javabudd
Copy link

@javabudd javabudd commented Nov 2, 2022

Q A
Documentation no
Bugfix no
BC Break no
New Feature no
RFC yes
QA no

Description

andyo and others added 5 commits November 1, 2022 11:49
Signed-off-by: andyo <andy@servicecore.com>
Signed-off-by: andyo <andy@servicecore.com>
Signed-off-by: andyo <andy@servicecore.com>
Signed-off-by: andyo <andy@servicecore.com>
…inas-hydrator

Signed-off-by: andyo <javabudd@gmail.com>
@javabudd
Copy link
Author

javabudd commented Nov 2, 2022

This PR branches off #33 to attempt to fix CI builds for PHP 8

@@ -37,6 +36,8 @@
*/
class CollectionListener implements ListenerAggregateInterface
{
public const CONFIG_NAMESPACE = 'doctrine-hydrator';
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This probably isn't the best place for this, thoughts?

{
if (! $this->hydrator) {
// FIXME: find a way to test this line from a created API. Shouldn't all created API's have a hydrator?
$this->hydrator = new Hydrator\DoctrineObject($this->getObjectManager(), $this->getEntityClass());
$this->hydrator = new DoctrineObject($this->getObjectManager());
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The 2nd argument passed into this constructor has always been incorrect. It was supposed to be whether to use byValue hydration or not.

@javabudd javabudd closed this Nov 2, 2022
@javabudd
Copy link
Author

javabudd commented Nov 2, 2022

Declining in favor of #29

@javabudd javabudd reopened this Aug 28, 2023
@javabudd
Copy link
Author

javabudd commented Aug 28, 2023

Reopening this PR as #29 has become stale and other PR's to address this issue are using incorrect hydrator libraries.

@ajgale
Copy link

ajgale commented Aug 28, 2023

+1 on this as it is still preventing much needed PHP 8 upgrade

@speby
Copy link

speby commented Sep 14, 2023

Also +1 on this

@datasage
Copy link
Contributor

Please push this through. Will help get the rest of the project up to PHP 8.1/8.2

@davidwindell
Copy link

Is this likely to get merged anytime soon @Ocramius @weierophinney? We are starting a new API Tools project and would be good to have some direction. Thank you!

@davidwindell
Copy link

@javabudd I see you are still targeting PHP 8.0 (not 8.1). I guess this repo is abandoned now, so we'll roll our own Doctrine integration.

@TomHAnderson
Copy link
Contributor

TomHAnderson commented Nov 28, 2023

I was the original author of this repository. And I'm a principal on doctrine-laminas-hydrator. Since I left this project I've seen very little movement on this repository. That is unfortunate.

I've moved on to GraphQL now. @davidwindell if you're starting a new project I would encourage you to consider GraphQL. My integration library is here: https://github.com/API-Skeletons/doctrine-orm-graphql

@davidwindell
Copy link

Thanks for the ping @TomHAnderson. REST makes more sense for our use case but will certainly bear doctrine-orm-graphql in mind for future projects 👍

@javabudd
Copy link
Author

javabudd commented Nov 28, 2023

I was the original author of this repository. And I'm a principal on doctrine-laminas-hydrator. Since I left this project I've seen very little movement on this repository. That is unfortunate.

I've moved on to GraphQL now. @davidwindell if you're starting a new project I would encourage you to consider GraphQL. My integration library is here: https://github.com/API-Skeletons/doctrine-orm-graphql

I would be more than happy to assist with this repository, hence the pull request, but it seems nobody is willing to review or merge PR's anymore.

@datasage
Copy link
Contributor

I've been maintaining my own branches for forward compatibility. I can help with the effort needed to ensure that this repo is compatible with 8.2 and 8.3

@davidwindell
Copy link

We're spread very thin over here, heh.

@Ocramius thank you for these meeting minutes. I am shocked to read the "laminas-mvc seems to be almost dead" comment. I guess I need to catch up with the times and start looking at Mezzio.

@davidwindell
Copy link

FYI we ended up going with API Platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants