supergiant / supergiant-dashboard

94%

master: 94%

LAST BUILD ON BRANCH sort-components-fix

branch: sort-components-fix

CHANGE BRANCH

x

Reset

• sort-components-fix
• accept-api-components
• app-creation-fix
• apps-coverage
• components_apps_tasks_polish
• container-form-fix
• custom-deploy-script
• feedback_and_community
• master
• port-per-instance
• remove-color-picker
• send-repo-params
• skeletor
• v0.5.15
• v0.5.16-rc0
• v0.5.17
• v0.5.18
• v0.6.0
• v0.6.1
• v0.7.1
• v0.7.3
• v0.7.4
• v0.7.5

Build # 217

Build Type

push

travis-ci

Committed by esmevane

Commit Message

Correctly partition components on app name.

The previous method of approaching component / app sorting was a naive
approach.  It presumed that apps would have more or less distinct names.
That hasn't really been the case, however - so in instances where the
app names were very similar, a given component would appear in multiple
places.

This commit makes a little more of an intelligent guess out of the whole
thing - but ultimately what we really need to do in the long term will
be to organize components in a much more distinct way.  Either we can
give them a better keying interface on the back end or we can invent one
custom to the front-end using the tags feature.

Run Details

2603 of 2769 relevant lines covered (94.01%)

4.9 hits per line