[BUG] [Jave Service] java service should suport version fallback for all v1 & v2 api
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 72
- Forks
- 69
- Avg merge
- 23h 32m
- Merged PRs (30d)
- 4
Description
Describe the bug
[BUG] [Jave Service] java service should suport version fallback for all v1 & v2 api
To Reproduce
Steps to reproduce the behavior:
- such as go to 'translation-product-component-key-api'
- input version = 6.6.0
- see response
Expected behavior
"response": {
"code": 604,
"message": "Version has been fallen back: OK"
},
commit : https://github.com/vmware/singleton/commit/ea05b63f2c66ec90bd32cf60187fbe0125b46922
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.
Research direction
Start by reviewing commit ea05b63f2c66ec90bd32cf60187fbe0125b46922 and the Java service handling the translation-product-component-key-api request. Reproduce the request with version 6.6.0, then check the other v1 and v2 API paths for the expected version-fallback response with code 604.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100