Details
-
Improvement
-
Resolution: Fixed
-
None
-
High
-
Fixed naming scheme for Okapi Service Configuration Entries. In the frontend, no name must be defined anymore
-
Empty show more show less
Description
The naming-scheme of OKAPI service entries has changed and now is fixed, see https://bitbucket.org/mittagqi/translate5/pull-requests/734
The realm of this issue is, to make sure, the Frontend editing of the Configs (editor_Plugins_Okapi_DbConfig_OkapiConfigType)
and the commands to manage OKAPI service entries (OkapiUpdateCommand, OkapiAddCommand) respect the adjusted service structure.
It should not be possible to add other Okapi-versions than defined in editor_Plugins_Okapi_Init::SUPPORTED_OKAPI_VERSION other then for DEV purposes
Attachments
Issue Links
- relates to
-
TRANSLATE-2063 Enable parallele use of multiple okapi versions to fix Okapi bugs
- Done
-
TRANSLATE-2574 Enhance okapi-driven error message with defect docx-files coming from Google
- Open
-
TRANSLATE-3202 Adopt File Format Settings for OpenXML to Okapi version 1.4.7
- Final pull request