EZEE-2661: Allowed translation filtering when publishing version

[ViniTou]

Question	Answer
JIRA issue	EZEE-2661
Bug/Improvement	yes
New feature	yes
Target version	7.5 (2.5.1)
BC breaks	no
Tests pass	yes
Doc needed	yes

As a part of fix, we decided to add possibility to publish specific translations only.
As it seems more clearer now, I have decided to move previous logic from Handler inside ContentService and resolve it on API level.

TODO:

• Implement feature / fix a bug.
• Implement tests.
• Fix new code according to Coding Standards ($ composer fix-cs).
• Ask for Code Review.

[pspanja]

This really looks like a hack on top of a system that doesn't support versioning per translation. Because of that it comes with a number of weird edge cases. The first one that came to my mind - what happens when you edit a Content with 2 translations, you change the 1st translation but then proceed to publish the 2nd translation?

It would be easy to implement this on top of the Public API. What is the reason for adding it here, instead of implementing it for example in the date-based publisher? The similar question goes for #2598

[ViniTou]

@pspanja

what happens when you edit a Content with 2 translations, you change the 1st translation but then proceed to publish the 2nd translation?

You will end with published version identical to that one without changes to 1st translation. Would you as a user expect different behavior?

What is the reason for adding it here, instead of implementing it for example in the date-based publisher?

To have consistent publish action across places.

[pspanja]

You will end with published version identical to that one without changes to 1st translation. Would you as a user expect different behavior?

Not really, it's what I would expect, it's just that this adds another layer of meaning to the whole thing (publishing drafts/fields/translations). I guess it's a matter of how you approach the whole thing, I tend to think Repository should be made as simple and straightforward as possible, and specific behavior should be implemented on top of it. But it's not really my prerogative anymore, so in any case, thanks for the reply 👍

[micszo]

Current status:
Flow from https://jira.ez.no/browse/EZEE-2661 - OK.
Flow from https://jira.ez.no/browse/EZP-29694?focusedCommentId=240646&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-240646 - NOK.

[lserwatka]

@ViniTou could you look into this test results?

[micszo]

Tested on eZ Platform EE v2.5.1 together with the other 3 PRs.
The four test flows, as described below, work with these changes:
https://jira.ez.no/browse/EZP-29691
https://jira.ez.no/browse/EZP-29694
https://jira.ez.no/browse/EZP-29694?focusedCommentId=240646&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-240646
https://jira.ez.no/browse/EZEE-2661