Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation clarification #81

Open
cdaguerre opened this issue Jun 27, 2016 · 1 comment
Open

Documentation clarification #81

cdaguerre opened this issue Jun 27, 2016 · 1 comment

Comments

@cdaguerre
Copy link
Member

@aponsin Could you please clarify the difference between these routes:

Please note that according to documentantion, the route public/countries/ doesnt require a locale although it should be public/countries/{locale} (Refer https://fr.textmaster.com/documentation#public-listing-localized-country-names)

/cc @jmleroux

@aponsin
Copy link

aponsin commented Jun 27, 2016

We are talking about different things here:

  • locales
  • countries
  • abilities

The 2 locales end point are essentially the same. But please usr /public/locales the other one is still there fore backward compatibility reasons only. But they essentially return the same data (almost).

The countries end point does not make the locale mandatory, it will default on the English names if not specified. But if you want to specify a locale you can, in order to get the name of the countries in French, or German, etc.

Finally the Abilities end point is really only there to let one know what "abilities" (read combination of Activity, Level and Language Pair) are currently available on the platform and their associated cost.

I hope this helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants