-
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
PacketViewer config bugs #1806
PacketViewer config bugs #1806
Changes from all commits
b7b6bb1
4b7d72c
20aaa1f
543d1f6
cefeac0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -323,6 +323,24 @@ export default { | |
}, | ||
}, | ||
watch: { | ||
initialTargetName: function (val) { | ||
// These three "initial" watchers are here in case the parent component doesn't figure out its initial values | ||
// until after this component has already been created. All this logic incl. the "on-set" events could be | ||
// simplified with a refactor to use named v-models, but that's probably a significant breaking change. | ||
if (val) { | ||
this.selectedTargetName = val.toUpperCase() | ||
} | ||
}, | ||
initialPacketName: function (val) { | ||
if (val) { | ||
this.selectedPacketName = val.toUpperCase() | ||
} | ||
}, | ||
initialItemName: function (val) { | ||
if (val) { | ||
this.selectedItemName = val.toUpperCase() | ||
} | ||
}, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So this is the bug fix because we were updating There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Discussed during scrum, but I'm not sure how this ever worked, but I suspect the TargetPacketItemChooser was being destroyed and recreated or something like that. |
||
mode: function (newVal, oldVal) { | ||
this.selectedPacketName = null | ||
this.selectedItemName = null | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice ... I think there's probably other places in COSMOS where we're "remembering" previous values but the most obvious is here in Packet Viewer