Error in API call

[ToferC]

Hi Grant - first of all - great work on the crate. I had set it up and was using it in testing in an Actix-Web app and it was working well, but a few days ago it stopped working with the following error:

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ParseError("Unable to find translatedText in parsed JSON")', src/main.rs:172:101

I'm thinking there might have been a change in the LibreTranslate API

Here's the test snippet that mirrors my app:

use libretranslate::{translate, Language};

#[tokio::main]
async fn main() {
    let mut translate_strings: Vec<String> = Vec::new();

    let nodes = vec![
        ("father", "person"),
        ("manager", "role"),
        ("gen x", "person"),
    ];
    
    for n in &nodes {
        translate_strings.push(format!("{}.\n", &n.0));
    };

    let source = Language::English;
    let target = Language::French;

    let input = translate_strings.concat();

    let data = translate(source, target, input)
        .await
        .unwrap();

    let mut phrases: Vec<(String, String)> = Vec::new();

    //let en = data.input.split(". ").into_iter();
    let fr = data.output.split(".\n");
    let en = data.input.split(".\n");

    for (f, e) in fr.zip(en) {
        if e != "" {
            phrases.push((e.to_lowercase().replace("/", ""), f.to_lowercase().replace("/","")));
        };
    };

    println!("{:?}", &phrases);

[PJ-Finlay]

LibreTranslate/LibreTranslate#82

@pierotofy

[PJ-Finlay]

It may make sense to point the default rust bindings to one of the mirrors instead of libretranslate.com to take pressure off the main site.

[pierotofy]

Yeah ideally any bindings library should allow developers to choose a host to point to (and to not default to libretranslate.com).

We'd love to be able to provide a public API translation for everyone, but it's just not sustainable.

You can still use the API endpoints from libretranslate.com, but now you need an API key for programmatic access.

[ToferC]

Makes perfect sense, @pierotofy. I'd suggest the requirement should be documented in the crate and a clearer error message be transmitted back.

[grantshandy]

Hey thanks for all this, I'll make the changes now.

[grantshandy]

Hey thanks for the issue, I should have solved the problem.

You can now translate using a custom URL, as well as get better errors from the website.

See the example.

Does this fix your problem? @ToferC, @pierotofy & @PJ-Finlay

[ToferC]

Thanks @grantshandy - fixes look great.