Closed (fixed)
Project:
Translation Management Tool
Version:
8.x-1.x-dev
Component:
Translator: Local
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
20 May 2016 at 15:35 UTC
Updated:
15 Jul 2016 at 22:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
edurenye commentedDone and added tests.
Comment #3
miro_dietikergetAssignee() thus has a wrong annotation. It needs to add null as a return option.
Also the code reads like this bug would make the form fail fatal if there is no assignee. Thus we would need test coverage for the bug.
Other than that, this patch looks really nice.
Additionally, the issue reminded me to the fact that our Provider UI should somehow list that / if a provider supports continuous operation or not.
Created issue #2735439: Display translator capabilities
Comment #4
edurenye commentedAdded NULL and test for the fix in the LocalTaskForm (see test_only file).
Comment #5
miro_dietikerI think it's null, not NULL in phpdoc. ;-)
Comment #6
edurenye commentedDone.
Comment #7
berdiris empty items something the translator needs to be project against? I think not when combined with the other issue that doesn't call requestTranslation() in that case?
I don't really get why you add a manual job item, continuous is supposed to do that automatically for you? Don't you end up with two job items now?
Comment #8
Bambell commentedI'm not exactly sure why, but the job item wouldn't get created after creating the node. I changed the node type and how the node is created as a workaround to this. Mostly copied from
Drupal\Tests\tmgmt_content\Kernel\ContentEntitySourceUnitTest\testContinuousJobItems.Comment #9
edurenye commentedLooks good to me, so RTBC.
Comment #10
berdirI guess this was the missing part, yes.
Looks good to me as well.