Skip to content

add php 7.4 support (update jms serializer v3 + phpUnit) + fix issue 41#54

Closed
medliii wants to merge 2 commits intoallure-framework:masterfrom
medliii:master
Closed

add php 7.4 support (update jms serializer v3 + phpUnit) + fix issue 41#54
medliii wants to merge 2 commits intoallure-framework:masterfrom
medliii:master

Conversation

@medliii
Copy link

@medliii medliii commented Mar 1, 2020

Plus fix 41 via change

public static function registerAnnotationNamespaces() { AnnotationRegistry::registerUniqueLoader('class_exists'); }

doctrine/annotations 2 won't support AnnotationRegistry::register*
And this behavior will be by default
doctrine/annotations#205

@medliii medliii changed the title add php 7.4 support (update jms serializer v3 + phpUnit) + fix issue [41](https://github.com/allure-framework/allure-php-commons/issues/41) via change add php 7.4 support (update jms serializer v3 + phpUnit) + fix issue 41 Mar 1, 2020
]
);

AnnotationRegistry::registerAutoloadNamespace(
Copy link
Author

Choose a reason for hiding this comment

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

This functions are deprecated

@techhemant
Copy link

I hope this gets fixed ASAP. It's an obstacle for our test runs.

* @expectedException Exception
*/
public function testExecuteFailingStep()
public function te1stExecuteFailingStep()

Choose a reason for hiding this comment

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

Change this back to testExecuteFailingStep

Copy link
Author

Choose a reason for hiding this comment

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

fixed

@techhemant
Copy link

@medliii Do you have proof of it working with real phpunit test? Can you share screenshots of the same?

@CLAassistant
Copy link

CLA assistant check
All committers have signed the CLA.

@eroshenkoam eroshenkoam added the type:dependencies Pull requests that update a dependency file label Mar 12, 2020
@remorhaz
Copy link
Contributor

Bump! Is there any way for me to help with accepting this PR?

Copy link
Member

@baev baev left a comment

Choose a reason for hiding this comment

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

why delete composer.lock?

@remorhaz
Copy link
Contributor

remorhaz commented Aug 24, 2020

why delete composer.lock?

I don't know the original author's intention, but in general it's useless or even harmful to keep composer.lock in libraries. When the package is installed as a library, it's lock file is ignored; that means that "stable" combination of dependencies that was tested is never preserved. So I'd rather advice to delete it, too.

@baev
Copy link
Member

baev commented Aug 24, 2020

@remorhaz thanks for clarification

@medliii could you please fix merge conflicts?

@remorhaz
Copy link
Contributor

This PR seems to be abandoned, so I've resolved conflicts in another PR #65.

@baev
Copy link
Member

baev commented Jan 21, 2021

closed via #65

@baev baev closed this Jan 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type:dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support for JMS\Serializer >= 2.0.0

6 participants