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

Convert MageBraintree to use the serializer rather than Zend_Json #8393

Closed
wants to merge 2 commits into from

Conversation

dmanners
Copy link
Contributor

@dmanners dmanners commented Feb 2, 2017

As Zend1 is end of life usage of Zend_Json should be converted to the internal serializer in Magento2

@ishakhsuvarov ishakhsuvarov self-assigned this Feb 2, 2017
Copy link
Contributor

@ishakhsuvarov ishakhsuvarov left a comment

Choose a reason for hiding this comment

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

Currently we can not accept majority of the changes which modify the constructor signature.
This requirement is introduced to maintain maximum compatibility with already existing extensions and customizations, potentially relying on the class via extending.

@ishakhsuvarov
Copy link
Contributor

ishakhsuvarov commented Feb 2, 2017

@dmanners Currently we can not accept majority of the changes which modify the constructor signature.
This requirement is introduced to maintain maximum compatibility with already existing extensions and customizations, potentially relying on the class via extending.

To add a new parameter to the constructor you may introduce it as optional, for example:

public function __construct(
    \Magento\Framework\Serialize\SerializerInterface $serializer = null
) {
    $this->serializer = $serialize ?: \Magento\Framework\App\ObjectManager::getInstance()->get(\Magento\Framework\Serialize\SerializerInterface::class);
}

@dmanners
Copy link
Contributor Author

dmanners commented Feb 2, 2017

Thanks for the feedback @ishakhsuvarov I guess that covers all the other zend_json PRs I have put in over the last few days.

@ishakhsuvarov
Copy link
Contributor

@dmanners Thank you for the update. We are going to proceed with processing now.

@okorshenko
Copy link
Contributor

@dmanners Thank you for your contribution to Magento 2 project! Your pull request has been successfully merged! For some reason, we have different your commit hashes that's why this PR is not closed. But your changes already on develop branch. Thank you

@okorshenko okorshenko closed this Feb 4, 2017
@dmanners
Copy link
Contributor Author

dmanners commented Feb 5, 2017

@okorshenko thanks. It is probably cause I like to keep my branches up to date and regularly rebase them. You may have merged an older version or something. No issue there as there where no new commits added after the rebase.

@okorshenko okorshenko added this to the February 2017 milestone Feb 11, 2017
@dmanners dmanners deleted the remove-zend-json-braintree branch July 26, 2017 12:00
magento-devops-reposync-svc pushed a commit that referenced this pull request Sep 7, 2023
…fix-07112023

cia-2.4.7-beta2-develop-bugfix-07112023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants