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 #16503 - composite view ui - newer component version exists #6310

Merged
merged 1 commit into from Sep 13, 2016

Conversation

bbuckingham
Copy link
Member

Update the composite content view UI to let the user know
if a newer version of a component content view exists.

@bbuckingham
Copy link
Member Author

The following is an example of the UI with the change:
newer_version

@@ -33,6 +33,13 @@ angular.module('Bastion.content-views').controller('ContentViewCompositeContentV
return deferred.promise;
};

$scope.newerVersionExists = function (contentViewVersion) {
var found = _.find(contentViewVersion['content_view']['content_view_version_ids'], function(num) {
Copy link
Member

Choose a reason for hiding this comment

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

With incremental update, the idea of a 'newer' version is somewhat muddled. Is it by version #? or just last published?

I would think it'd be by version number (i.e. 3.0 is newer than 2.2) even if the greater number was published before the lesser numbered version.

Copy link
Member Author

Choose a reason for hiding this comment

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

Good point. It is actually using the database id, which implies the most recent version published. In the example above, that would mean 2.2 is newer than 3.0.

Update the composite content view UI to let the user know
if a newer version of a component content view exists.
@bbuckingham
Copy link
Member Author

@jlsherrill, updated the PR to base latest off of major version. Below is an updated screenshot for reference:

latest_version_based_on_major

@jlsherrill
Copy link
Member

ACK

@bbuckingham bbuckingham merged commit 7aa6f73 into Katello:master Sep 13, 2016
@bbuckingham bbuckingham deleted the issue-16503 branch September 13, 2016 21:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants