Repository navigation
Show canonical task names in links and preserve exact selection - #627
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The task chip in a completion message showed a generated identifier while its panel showed the desktop-tray title. The metadata route queried only legacy
hasName, so it missed the task's canonical#V#hasNametitle. Read both spellings in one bounded query and preserve existing stored names when no relation names are available. Link identities and task-selection behaviour are unchanged.Live diagnosis also found that this native tray task had been created with
JVNAUTOSCI-2740, the separate worker-setup issue, as its reference code. That incorrect badge was removed through the canonical task service with an audit note; its identity, instructions, status and assignment were verified unchanged.Validation: seven backend route tests and 18 frontend tests passed, including canonical/legacy naming, exact task identity, and an older task response arriving after a newer selection. An isolated Messages browser replay using the actual DGX task and candidate metadata confirmed matching link/panel titles, removal of the incorrect badge, refresh, task button, reference menu, focus and draft preservation. Deployment and exact live read-back follow merge under the user's explicit request.
Tracking: https://naoinstitute.atlassian.net/browse/JVNAUTOSCI-2744