Skip to content

Conversation

dverkade
Copy link
Member

@dverkade dverkade commented Nov 3, 2017

Description

Fixed Issues

  1. Why does \Magento\Translation\Model\Js\DataProvider use \Magento\Framework\Phrase\Renderer\Translate, not \Magento\Framework\Phrase\Renderer\Composite? #2156: Why does \Magento\Translation\Model\Js\DataProvider use \Magento\Framework\Phrase\Renderer\Translate, not \Magento\Framework\Phrase\Renderer\Composite?

- Changed InlineTest, which has an Inline class object and not a Translate class object
@magento-engcom-team magento-engcom-team added 2.2.x bugfix Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release labels Nov 7, 2017
@ihor-sviziev ihor-sviziev self-assigned this Nov 10, 2017
@ihor-sviziev ihor-sviziev added Release Line: 2.2 Progress: accept Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Nov 10, 2017
@ihor-sviziev
Copy link
Contributor

ihor-sviziev commented Nov 10, 2017

@dverkade could you please create the same PR to 2.1-develop and 2.2-develop branches?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix Fixed in 2.3.x The issue has been fixed in 2.3 release line Progress: accept Release Line: 2.3 Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants