I’ve found that extending
/languages
to include an additionaltargets
field should work without breaking backward compatibility and without needing an additional endpoint. I’ll modify the JS client as well and do some checks server side. #358
[{"code":"en","name":"English","targets":["it","ar","zh","nl","fi","fr","de","hi","hu","id","ga","ja","ko","pl","pt","ru","es","sv","tr","uk","vi","az","cs","eo","el","he","fa","sk","da","en"]},{"code":"ar","name":"Arabic","targets":["en","ar","it","zh","nl","fi","fr","de","hi","hu","id","ga","ja","ko","pl","pt","ru","es","sv","tr","uk","vi","az","cs","eo","el","he","fa","sk","da"]},
I like this solution.
I also figured out that the English->Catalan issue was a bug in the package index.