On Jan 24, 2015, at 01:42 PM, Sumana Harihareswara wrote:
>Expose ILanguageManager as a REST resource, so that Postorius can use it
>to learn what languages a system supports
Since languages must be enabled in the config files, they are system
resources, so they should probably live under the <api>/system/languages
resource, which would be read-only. GETing that would return the collection
of languages as resource entries. Individual languages could be GET'd via
their code, e.g. <api>/system/languages/it
Each language resource would return a JSON representation containing the code,
charset, and description. See ILanguage for that specification.
(Even though ILanguageManager supports .add(), exposing this to the API
doesn't make them persistent so I don't think POST, PATCH, or PUT should be
exposed in the REST API on that resource.)
On Jan 24, 2015, at 01:42 PM, Sumana Harihareswara wrote:
>Expose ILanguageManager as a REST resource, so that Postorius can use it
>to learn what languages a system supports
Since languages must be enabled in the config files, they are system languages languages/ it
resources, so they should probably live under the <api>/system/
resource, which would be read-only. GETing that would return the collection
of languages as resource entries. Individual languages could be GET'd via
their code, e.g. <api>/system/
Each language resource would return a JSON representation containing the code,
charset, and description. See ILanguage for that specification.
(Even though ILanguageManager supports .add(), exposing this to the API
doesn't make them persistent so I don't think POST, PATCH, or PUT should be
exposed in the REST API on that resource.)