-
Notifications
You must be signed in to change notification settings - Fork 0
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
Deviant experiment support #18
Conversation
|
||
setActiveSegmentIds(segmentIds?: api.WorkspaceSegmentId[]) { | ||
if (segmentIds && segmentIds.length == 1) { | ||
this.activeSegmentId = segmentIds[0]; |
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.
This is a little different from what we do elsewhere, with multiple active segments. Is there no other reasonable behavior here?
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.
I started with following the existing pattern we have for spec eval summaries as a starter.
We can certainly expand this (and mutations/etc) to handle multiple active segments.
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.
I added a ticket to the board for it.
Based on #17