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
Implement skeleton for Test Details Views #44
Conversation
As of now, we have a working structure. Specific data like the content for Hero (and an alternative collapsed Hero), test details come from its own Also added a collection called @hellais Please review and point out holes in this approach. |
I took a look at the code as well and this approach looks solid to me 👍 |
Is it useful if I make a mockup of how the views in collapsed vs expanded form shall look like? |
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.
Looks good to me
I suggest to merge this PR and then follow up with others! |
I had made some changes to the approved model because I immediately found a problem with it. I will send them for review here in the next few minutes. |
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.
Looks good! I've added some quick suggestions I'd like to be applied before merging!
🐳
@@ -89,6 +91,24 @@ export const testGroups = { | |||
} | |||
} | |||
|
|||
export const tests = { | |||
web_connectivity, |
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 syntactic sugar for web_connectivity: web_connectivity
, right?
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.
That's correct.
return ( | ||
<div> | ||
{render({ | ||
heroBG: 'green8', // TODO: Determine color based on presence of anomaly |
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.
Suggested // TODO(sarathms): ...
so we know who's owning the TODO
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.
Added
whatsapp: web_connectivity, | ||
ndt: web_connectivity, | ||
dash: web_connectivity, | ||
vanilla_tor: web_connectivity, |
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.
If your goal is to later replace each of them, please add a TODO(sarathms): ...
comment to indicate that.
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.
Added TODO
@@ -97,32 +99,144 @@ const HeaderContent = styled(Box)` | |||
-webkit-app-region: drag; | |||
` | |||
|
|||
const detailsMap = { | |||
web_connectivity: WebConnectivity, | |||
facebook_messenger: FacebookMessengerDetails |
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.
Does this mean that more will come later? If so, please add a // TODO(sarathms): ...
comment to say that
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.
Added
Implements 1 out of 7 views listed in #3