Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-2195

InstantTranslate filepretranslation API has a wrong parameter name

    • Medium
    • Hide
      Supertext informieren, dass sie den Parameter in ihrer API entsprechend anpassen können - bei Weiterführender Nutzung von 0 bekommen Sie deprecated Warnungen.
      https://jira.translate5.net/browse/TS-506
      Show
      Supertext informieren, dass sie den Parameter in ihrer API entsprechend anpassen können - bei Weiterführender Nutzung von 0 bekommen Sie deprecated Warnungen. → https://jira.translate5.net/browse/TS-506

      problem

      When using the InstantTranslate5 filepretranslation via the API endpoint
      /editor/instanttranslateapi/filepretranslation
      the POST is sent as multipart/form-data. According to the Documentation the name of parameter should be "file" but indeed it is currently "0". 

      solution

      This must be changed:

      1. In Documentation - there is currently the problem explained
      2. In the API Endpoint (but keep the index "0" working for legacy API users and log a warning)
      3. Change the field in the IntantTranslate GUI code

          [TRANSLATE-2195] InstantTranslate filepretranslation API has a wrong parameter name

          Transition Time In Source Status Execution Times
          Thomas Lauria made transition -
          Open Selected for dev
          1m 12s 1
          Marc Mittag [Administrator] made transition -
          Final pull request Selected for dev
          3d 18h 24m 1
          Aleksandar Mitrev made transition -
          Selected for dev In Progress
          16d 1h 36m 2
          Aleksandar Mitrev made transition -
          In Progress Final pull request
          10s 2
          Marc Mittag [Administrator] made transition -
          Final pull request Done
          1d 6h 36m 1

            aleksandar Aleksandar Mitrev
            tlauria Thomas Lauria
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: