OpenLiberty / OpenLiberty/liberty-tools-eclipse
MicroProfile Rest Client properties: followRedirects, etc. not shown in completion in microprofile-config.properties editor
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 16
- Forks
- 20
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 16
Description
Using LTE v24.0.12,
I can get completion for a set of MP Rest Client properties, but not, however for:
client.MyClient/mp-rest/followRedirects=true in the microprofile-config.properties file.
I had to search and finally found the syntax in:
https://openliberty.io/blog/2021/03/24/whats-new-in-MP-Rest-Client2.0.html
Looking at the MP RC spec it looks like these three are missing:
- com.mycompany.remoteServices.MyServiceClient/mp-rest/followRedirects: A boolean value (Any value other than "true" will be interpreted as "false") used to determine whether the client should follow HTTP redirect responses.
- com.mycompany.remoteServices.MyServiceClient/mp-rest/proxyAddress: A string value in the form of : that specifies the HTTP proxy server hostname (or IP address) and port for requests of this client to use.
- com.mycompany.remoteServices.MyServiceClient/mp-rest/queryParamStyle: An enumerated type string value with possible values of "MULTI_PAIRS" (default), "COMMA_SEPARATED", or "ARRAY_PAIRS" that specifies the format in which multiple values for the same query parameter is used.
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 locating the completion definitions for MicroProfile Rest Client properties in the microprofile-config.properties editor and compare them with the referenced MicroProfile Rest Client specification. The work is done when completion includes followRedirects, proxyAddress, and queryParamStyle with their documented values and descriptions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100