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

Fix header component - Closes #506 #542

Merged
merged 4 commits into from Aug 1, 2017
Merged

Fix header component - Closes #506 #542

merged 4 commits into from Aug 1, 2017

Conversation

alepop
Copy link
Contributor

@alepop alepop commented Aug 1, 2017

  • Add <PrivateWrapper /> component
  • Handle logout action on Logout button click
  • Align drop-down menu
    close Fix Header component #506

@slaweet slaweet added the bug label Aug 1, 2017
@slaweet slaweet added this to Pending Review in Version 1.1.0 Aug 1, 2017
Copy link
Contributor

@yasharAyari yasharAyari left a comment

Choose a reason for hiding this comment

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

good job.

@yasharAyari yasharAyari merged commit 9b50d4e into LiskArchive:development Aug 1, 2017
);

const mapStateToProps = state => ({
isAuthenticated: !!state.account.publicKey,
Copy link
Contributor

Choose a reason for hiding this comment

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

this should be something else then publicKey because now it shows the haeder right when I click the "Login" button, but it should only after the server request is finished and it is redirected from login page.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

currently, all private routes look to the same params.

Copy link
Contributor

@slaweet slaweet Aug 1, 2017

Choose a reason for hiding this comment

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

In private routes, it makes no user-visible difference. But on the login page if user is on slower network, it can longer time for the request and only then user is redirected from login page. Logout and Send buttons should not be on login page in the meantime.

Copy link
Contributor

Choose a reason for hiding this comment

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

This was fixed in the meantime by some other changes.

@@ -39,7 +39,7 @@ class Transactions extends React.Component {
length: parseInt(res.count, 10),
});
})
.catch(error => console.error(error.message));
.catch(error => console.error(error.message)); //eslint-disable-line
Copy link
Contributor

Choose a reason for hiding this comment

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

I see that finally somebody got annoyed enough by the warning in console :-) Though I would prefer to disable the specific rule. In this case a believe it is //eslint-disable-line no-console

@@ -16,3 +16,7 @@
.material-icons{
font-size: 24px !important;
}

.menu {
right: -16px !important;
Copy link
Contributor

Choose a reason for hiding this comment

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

This could be less (maybe right: -8px !important;) and the put the rest on .wrapper.
.wrapper has too much space on the right compared to nano 1.0.0 and not enough at the bottom.

I mean something like this is missing

.wrapper {
  margin-right: -8px;
  margin-bottom: 16px;
}

Copy link
Contributor Author

Choose a reason for hiding this comment

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

menu is a theme param, and it passes to the component and merges with other styles. it is so hard to style Menu component through IconMenu component.

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

This is still an issue

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Do i need to fix it in other pr?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, please.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Version 1.1.0
Merged Pull Requests
Development

Successfully merging this pull request may close these issues.

Fix Header component
4 participants