[REQUIREMENT] [Go Service]should support customize config pseudo in config yaml ,same as java service
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] [Go Service]should support customize config pseudo in config yaml ,such as java service
To Reproduce
[BUG] [Go Service]should support customize config pseudo in config yaml ,such as java service ,below :
in java service cofig file ,
#pseudo.enabled=false
pseudo.existSourceTag=#@
pseudo.notExistSourceTag=@@
Expected behavior
1.if source no-existed , translation data like :
2.if source existed , translation data like :
commit https://github.com/vmware/singleton/commit/fb3c0bb0db9b2cac59097d3250c10e4cbf180998
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 with the linked commit and the Go service's YAML configuration handling, then compare its behavior with the Java service's pseudo settings. Done means the Go service supports equivalent customizable pseudo markers and produces the expected output for both missing and existing sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- internationalization, localization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100