Skip to content
This repository has been archived by the owner on Dec 17, 2019. It is now read-only.

Aerogear 7706 Add base build view to mobile client page #27

Merged
merged 6 commits into from
Aug 2, 2018

Conversation

StephenCoady
Copy link
Member

Changes

build

@StephenCoady StephenCoady changed the title Aerogear 7706 Aerogear 7706 Add base build view to mobile client page Jul 31, 2018
@coveralls
Copy link

coveralls commented Jul 31, 2018

Pull Request Test Coverage Report for Build 261

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 74.39%

Totals Coverage Status
Change from base Build 247: 0.0%
Covered Lines: 122
Relevant Lines: 164

💛 - Coveralls

@jhellar
Copy link
Contributor

jhellar commented Jul 31, 2018

In my browser, when I click the menu button, the menu is not displayed properly. Otherwise LGTM.

menu

Copy link
Member

@ciaranRoche ciaranRoche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just one question inline!

</React.Fragment>
);

const buildConfig = {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only a question here, is there a benefit to defining a const here over a function defined in the component itself returning the jsx?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is just the way Jan mocked the data for now. Once we have the backend hooked up this will be gone completely and props will be passed to this component.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typical the one I clicked on to leave the comment, I meant to call out either const actions or const heading, is there any benefit to having them here?

@@ -19,7 +92,7 @@ class Client extends Component {
<ConfigurationView />
</TabPane>
<TabPane eventKey={2}>
Builds
<MobileClientBuildOverviewList mobileClientBuilds={mobileClientBuilds}></MobileClientBuildOverviewList>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MobileClientBuildsList as a name?

What this list displays is a list of buildConfigs which can be got from /api/buildconfigs. Can you try using the endpoint instead of mock since it has been merged now?

@@ -0,0 +1,37 @@
import React, { Component } from 'react';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aware this isn't your component but maybe BuildConfigDetails as a name?



const actions = () => (
<React.Fragment id="mobile-client-actions" pullRight>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is id needed?


return (
<MobileListViewItem
className="overview-list-view-item"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

className isn't needed.

@sedroche
Copy link
Contributor

sedroche commented Aug 1, 2018

@StephenCoady A few things visually. The header size is different to the overview component as that header contains more elements/information. I think it might make sense to set a height on the header to keep them the same. It feels jarring having inconsistent components.

Also can you take a look at this component in the community release version and match the font sizing etc/icon styles etc.

<div className="build-config">
<Row>
<Col md={6}>
<b>Repo Url</b>
Copy link
Contributor

@sedroche sedroche Aug 1, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add semi colons on the <b>s?

@StephenCoady StephenCoady force-pushed the AEROGEAR-7706 branch 2 times, most recently from 2a3b942 to e16b81b Compare August 2, 2018 14:05
@StephenCoady
Copy link
Member Author

@sedroche addressed your comments.

Copy link
Member

@ciaranRoche ciaranRoche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good 👍

@StephenCoady StephenCoady merged commit d2d1525 into master Aug 2, 2018
@grdryn grdryn deleted the AEROGEAR-7706 branch January 7, 2019 12:14
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants