[BUG][Java Service]localeID is empty when requesting language goes with region and combinational locale is valid on language/region pattern api.
Open
@huihuiw01 is already working on this.
Since Jun 6, 2023.
area/java-service
kind/bug
priority/medium
- Dominant language
- Java
- Stars
- 72
- Forks
- 69
- Avg merge
- 23h 32m
- Merged PRs (30d)
- 4
Description
Describe the bug
commit: 3ca386100dcad77b1fb36031cc621726a94278ee
localeID is empty when requesting language goes with region and combinational locale is valid on language/region pattern api.
GET /i18n/api/v1/i18nPattern
GET /i18n/api/v2/formatting/patterns/locales/{locale}
To Reproduce
Steps to reproduce the behavior:
- Go to 'GET /i18n/api/v2/formatting/patterns'
- Input "en-US" as language, "US" as region and "plurals" as pattern.
- See the response:
{
"response": {
"code": 200,
"message": "OK",
"serverTime": ""
},
"signature": "",
"data": {
"localeID": "",
"language": "en-US",
"region": "us",
"categories":
...
}
}
Expected behavior
the combinational locale should be listed as localeID value: en-US
{
"response": {
"code": 200,
"message": "OK",
"serverTime": ""
},
"signature": "",
"data": {
"localeID": "en-US",
"language": "en-US",
"region": "us",
"categories":
...
}
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.