-
Notifications
You must be signed in to change notification settings - Fork 5
MET-6977 Chained Rerun Design #959
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
Conversation
jeortizquan
left a comment
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.
a suggestion, see if this applies.
|
|
||
| isAncestorMode(): boolean { | ||
| return this.sandboxNavConf[2].stepSubClass === 'ancestor-mode'; | ||
| return (this.sandboxNavConf[2].stepSubClass ?? '').includes(this.ANCESTOR_MODE); |
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.
suggestion this.sandboxNavConf[2] can be a variable to be accessed with a name? e.g.
this.sandboxNavConf[ITEM_NAME_BEING_ACCESSED] where const ITEM_NAME_BEING_ACCESSED=2
or
var navigationConfiguration = this.sandboxNavConf[2]
saying this from readability perspective when coming back and read the code we know what that 2 item means.
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.
You're right. I have plans to refactor this further in the future in the future.
No description provided.