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

Don't apply filters to node endpoints & update details panel logic #701

Merged
merged 1 commit into from
Nov 30, 2015

Conversation

tomwilkie
Copy link
Contributor

Such that node which disappear from the topology (eg when they are stopped) don't disappear from the details panel.

Fixes #693

…ch that node which dissappear from the topology (eg when they are stopped) don't dissapear from the details panel.
@davkal
Copy link
Contributor

davkal commented Nov 30, 2015

We're still sending the topology options as a request parameter:
https://github.com/weaveworks/scope/blob/693-no-filter-details/client/app/scripts/utils/web-api-utils.js#L104

Should that be removed too?

@tomwilkie
Copy link
Contributor Author

Yes it can be now. Do you mind doing that?

if (details) {
return this.renderDetails();
}

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

@tomwilkie
Copy link
Contributor Author

Test failures are fixed on master. Can I merge this now?

@paulbellamy
Copy link
Contributor

LGTM, then.

tomwilkie added a commit that referenced this pull request Nov 30, 2015
Don't apply filters to node endpoints & update details panel logic
@tomwilkie tomwilkie merged commit f16db9d into master Nov 30, 2015
@tomwilkie tomwilkie deleted the 693-no-filter-details branch November 30, 2015 11:59
@davkal
Copy link
Contributor

davkal commented Nov 30, 2015

Looks like I came too late: 40f5040 (removes options query from node details request)

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.

3 participants