-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Workflow] Editing a task label does not update the name property #1351
Labels
Comments
tortmayr
added a commit
to eclipse-glsp/glsp-server-node
that referenced
this issue
Jun 21, 2024
Update the NodeDocumentationNavigationTargetProvider to not rely on the tasks name which is currently unreliable (see eclipse-glsp/glsp#1351) and instead relies on the `text` property of the tasks label.
2 tasks
tortmayr
added a commit
to eclipse-glsp/glsp-server-node
that referenced
this issue
Jun 21, 2024
Update the NodeDocumentationNavigationTargetProvider to not rely on the tasks name which is currently unreliable (see eclipse-glsp/glsp#1351) and instead relies on the `text` property of the tasks label.
tortmayr
added a commit
to eclipse-glsp/glsp-server-node
that referenced
this issue
Jun 21, 2024
Update the NodeDocumentationNavigationTargetProvider to not rely on the tasks name which is currently unreliable (see eclipse-glsp/glsp#1351) and instead relies on the `text` property of the tasks label.
tortmayr
added a commit
to eclipse-glsp/glsp-server
that referenced
this issue
Jun 24, 2024
Update the NodeDocumentationNavigationTargetProvider to not rely on the tasks name which is currently unreliable (see eclipse-glsp/glsp#1351) and instead relies on the `text` property of the tasks label.
2 tasks
tortmayr
added a commit
to eclipse-glsp/glsp-server
that referenced
this issue
Jun 24, 2024
Update the NodeDocumentationNavigationTargetProvider to not rely on the tasks name which is currently unreliable (see eclipse-glsp/glsp#1351) and instead relies on the `text` property of the tasks label.
I suggest to handle this in combination with #1183 |
MatthiasHofstaetter
pushed a commit
to MatthiasHofstaetter/glsp-server
that referenced
this issue
Dec 16, 2024
Update the NodeDocumentationNavigationTargetProvider to not rely on the tasks name which is currently unreliable (see eclipse-glsp/glsp#1351) and instead relies on the `text` property of the tasks label.
MatthiasHofstaetter
pushed a commit
to MatthiasHofstaetter/glsp-server
that referenced
this issue
Dec 21, 2024
Update the NodeDocumentationNavigationTargetProvider to not rely on the tasks name which is currently unreliable (see eclipse-glsp/glsp#1351) and instead relies on the `text` property of the tasks label.
MatthiasHofstaetter
pushed a commit
to MatthiasHofstaetter/glsp-server
that referenced
this issue
Dec 21, 2024
Update the NodeDocumentationNavigationTargetProvider to not rely on the tasks name which is currently unreliable (see eclipse-glsp/glsp#1351) and instead relies on the `text` property of the tasks label.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently task nodes have a name property, that is intended to reflect the tasks name. However, changing a task name via label edit does only change the text of the label but does not update the property. This causes inconsistencies.
ApplyLabelEditHandler
that also changes the name in the underlying model.The text was updated successfully, but these errors were encountered: