Unsupported placeholders in messages
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
Describe the bug
There are a lot of messages in APIML that defines placeholder out of the text. The best example it this one:
These values would be definitelly helpfull for customers, but the message does not support replacement placeholder out of text field.
These values looks for customer like an error.
Simply solution is to replace these messages with a text (without a real value). The best solution is to add support to messages and set all required argmuents in each code that generates the message.
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 discovery-service/src/main/resources/discovery-log-messages.yml at the linked message range, then trace the code that generates those messages. Decide whether the affected messages should use plain text or supported replacement arguments, and verify that the selected messages no longer expose unsupported placeholders to customers.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100