-
Notifications
You must be signed in to change notification settings - Fork 230
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
Sort bindingsByInstanceRef by first associated application #1742
Sort bindingsByInstanceRef by first associated application #1742
Conversation
app/scripts/controllers/overview.js
Outdated
overview.bindingsByInstanceRef = _.reduce(overview.bindingsByInstanceRef, function(result, bindingList, key) { | ||
result[key] = _.sortBy(bindingList, function(binding) { | ||
var apps = _.get(state.applicationsByBinding, [binding.metadata.name]); | ||
var sorted = _.sortBy(apps, 'metadata.name'); |
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.
It would be better to sort the applicationsByBinding list above instead of here. Then it's also sorted when expanding the provisioned service row in the overview.
01a892e
to
fc5528e
Compare
…om sorted applications)
@spadgett rebased, removed the extra I still am a little uncertain if the kind is handled/should be handled per doing this: |
[merge][severity:bug] |
Evaluated for origin web console merge up to cea541e |
Origin Web Console Merge Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_web_console/1578/) (Base Commit: 1e79956) (PR Branch Commit: cea541e) (Extended Tests: bug) |
Sort bindingsByInstanceRef by first associated application (from sorted applications)
Per @spadgett suggestion, sorting these in the overview controller so that they do not need to be resorted elsewhere.