Closed (fixed)
Project:
Translation Management Tool
Version:
7.x-1.x-dev
Component:
Core
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
18 Apr 2012 at 22:25 UTC
Updated:
15 Jul 2012 at 20:11 UTC
while working on supertext module I wanted to show the user a better explanation why his Job cannot be translated by the selected translator.
There is such a reason function for isAvailable: getNotAvailableReason() but not for the canTranslate function.
the attached patch adds this to tmgmt core.
The whole thing also depends on #1420364: A simple response object for methods which need to return a true/false *and* a message which then makes the reason functions obsolete. But until then I think we can add this.
| Comment | File | Size | Author |
|---|---|---|---|
| patch_commit_db8987531671.patch | 3.87 KB | schnitzel |
Comments
Comment #1
berdirpatch_commit_db8987531671.patch queued for re-testing.
Comment #2
berdirDecided to commit this.
While I'd prefer a solution based on the discussed return objects in the other issue, this is what we currently have a patch for and supertext already implements it. Easy to revert in case we implement the return objects.