Skip to content
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

Fixes host node/details panel color mismatch #880

Merged
merged 1 commit into from
Feb 1, 2016

Conversation

foot
Copy link
Contributor

@foot foot commented Jan 29, 2016

  • 'label_major' has been changed to 'label' in the details api response.
  • getNodeColorDark was giving up too early if a rank wasn't provided.
    The topo diagram which uses getNodeColor will select a color even w/
    no rank. Hosts don't have ranks at the mo.

Fixes #871

- 'label_major' has been changed to 'label' in the details api response.
- getNodeColorDark was giving up too early if a rank wasn't provided.
  The topo diagram which uses getNodeColor will select a color even w/
  no rank. Hosts don't have ranks at the mo.
@davkal
Copy link
Contributor

davkal commented Feb 1, 2016

Works as advertised, but the Loading... looks a bit pale

screen shot 2016-02-01 at 13 35 39

Can we do something about this?

@foot
Copy link
Contributor Author

foot commented Feb 1, 2016

I will do something about this!

@foot
Copy link
Contributor Author

foot commented Feb 1, 2016

No, I am having trouble doing something about this. Its white for my host-nodes! Clear-cache?

@davkal
Copy link
Contributor

davkal commented Feb 1, 2016

It seems like this style happens while react reconciliation gets interrupted by #891
So, this PR LGTM

foot added a commit that referenced this pull request Feb 1, 2016
Fixes host node/details panel color mismatch
@foot foot merged commit 5bd1907 into master Feb 1, 2016
@foot foot deleted the 871-host-node-color-mismatch branch February 1, 2016 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants