Skip to content

Property expression definition#19

Merged
angelozerr merged 1 commit intoeclipse-lsp4mp:masterfrom
datho7561:333-property-expression-definition
Sep 3, 2020
Merged

Property expression definition#19
angelozerr merged 1 commit intoeclipse-lsp4mp:masterfrom
datho7561:333-property-expression-definition

Conversation

@datho7561
Copy link
Copy Markdown
Contributor

@datho7561 datho7561 commented Jul 22, 2020

You can now trigger Go To Definition inside ${...}, and it will navigate to the location where the property value is assigned in the properties file.

Closes redhat-developer/quarkus-ls#333.

Signed-off-by: David Thompson davthomp@redhat.com

@xorye
Copy link
Copy Markdown

xorye commented Jul 22, 2020

In this case, can we have the goto definition go to city instead of %prod.city?
goto_def_profile

@datho7561 datho7561 force-pushed the 333-property-expression-definition branch from 56105a1 to 8fc2140 Compare July 23, 2020 16:03
@datho7561 datho7561 force-pushed the 333-property-expression-definition branch 2 times, most recently from 3281eb6 to 56bea85 Compare July 31, 2020 15:43
@datho7561 datho7561 changed the title 333 property expression definition Property expression definition Aug 11, 2020
@datho7561 datho7561 force-pushed the 333-property-expression-definition branch from 56bea85 to 0037b81 Compare September 1, 2020 13:51
@datho7561 datho7561 marked this pull request as ready for review September 1, 2020 13:52
@angelozerr
Copy link
Copy Markdown
Contributor

angelozerr commented Sep 2, 2020

In this case, can we have the goto definition go to city instead of %prod.city?

For this use case we should have 3 definitions I think (city, %prod.city and %dev.city), no?

@datho7561
Copy link
Copy Markdown
Contributor Author

For this use case we should have 3 definitions I think (city, %prod.city and %dev.city), no?

I think this could be helpful, depending on how the client supports multiple definitions being sent from the server.

@datho7561
Copy link
Copy Markdown
Contributor Author

This is the behaviour in vscode if the server returns multiple definitions:

GoToAllDefinitions

I think being able to direct the user to the different definitions is helpful.

@datho7561 datho7561 force-pushed the 333-property-expression-definition branch from 0037b81 to 6387a6c Compare September 2, 2020 17:49
You can now trigger Go To Definition inside ${...},
and it will navigate to the location where the property
value is assigned in the properties file.

Closes redhat-developer/quarkus-ls#333.

Signed-off-by: David Thompson <davthomp@redhat.com>
@datho7561 datho7561 force-pushed the 333-property-expression-definition branch from 6387a6c to cc50cca Compare September 3, 2020 15:45
@angelozerr angelozerr merged commit d3fa497 into eclipse-lsp4mp:master Sep 3, 2020
@angelozerr angelozerr added the enhancement New feature or request label Sep 11, 2020
@angelozerr angelozerr added this to the 0.1.0 milestone Sep 11, 2020
@datho7561 datho7561 deleted the 333-property-expression-definition branch July 19, 2021 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Definition support for property expressions

3 participants