apertium / apertium/apertium-apy

More Consistent GET variables?

Open
#156 5 comments 0 reactions 0 assignees View on GitHub
help wanted question
Dominant language
Python
Stars
39
Forks
46
PR merge metrics
No merged PRs in 30d

Description

I noticed when using /translate, the get variable is "langpair" and it takes a value like "eng | spa".

When using /translateChain, the get variable is "langpairs" and it takes an argument like "eng | spa | fra"

I know the input is technically different but shouldn't the variables be more consistent for usage sake?

Also shouldn't there be some way for the API to pick appropriate middle languages on its own instead of requiring it to be specified. For example, depending on the quality of a language pair, sending "eng | fra" might mean using " eng | spa | fra" automatically since spa and fra are both romance languages and spa might have a high score in accuracy between both eng and fra.

edit: While the thought of a cleaned up interface is on the mind, what if /translate and /translateChain were both done with /translate . It would run the appropiate code based on whether it is fed "eng | spa | fra" or "eng | spa"

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.