REST client CodeLens only shows up for GET annotations.

[rzgry]

Currently the MicroProfile REST Client CodeLens only show up for paths annotated with @GET.

I think it makes sense to display them for other annotations like POST or PUT even though they cannot be accessed from the browser. (If possible maybe we could make CodeLens for POST/PUT etc. requests not clickable?)

IE. if u have a rest client with just a POST endpoint, you might still want the CodeLens to appear so you can quickly see the full URL that is configured by your mp-config.properties file.

[angelozerr]

I think it makes sense to display them for other annotations like POST or PUT even though they cannot be accessed from the browser. (If possible maybe we could make CodeLens for POST/PUT etc. requests not clickable?)

The main reason is that POST/PUT should not be clickable. I agree with you, POST/PUT CodeLens should appear but we need to manage click:

• solution 1: when you create a CodeLens, you set the openURICommandId to null

  lsp4mp/microprofile.jdt/org.eclipse.lsp4mp.jdt.core/src/main/java/org/eclipse/lsp4mp/jdt/core/jaxrs/JaxRsUtils.java

  Line 81 in ab86a54

  public static CodeLens createURLCodeLens(String baseURL, String rootPath, String openURICommandId, IMethod method,

• solution 2: the vscode-client is able to manage POST request. It should nice too if we could on client side manage parameters to fill wuth an UI dialog according the method parameters.

[fbricon]

if the solution to make the links not clickable is to just send a null/empty command, we should do that

[angelozerr]

if the solution to make the links not clickable is to just send a null/empty command, we should do that

It should work.

[rgrunber]

I can have a look.

[datho7561]

I've been working through the Quarkus super heros example, and this would be very nice to have. I thought the app/ the Quarkus dev mode was broken when the code lens didn't show up.

[JessicaJHee]

I'm interested in working on this issue!

[fbricon]

codelenses are only shown on GET requests because they're the only types of requests that make sense to provide a hyperlink to

[rgrunber]

I think we can have it show up, just that we need to make it non-clickable. #94 (comment) mentions there is a way to do that.