Feature #5322

[8] Nutupane: display errors on a per field basis

Added by Mike McCune about 3 years ago. Updated 6 months ago.

Status:New
Priority:Normal
Assigned To:Walden Raines
Category:-
Target version:Katello - Team Tom - backlog
Difficulty: Pull request:
Bugzilla link:
Story points-
Velocity based estimate-
ReleaseBacklogRelease relationshipAuto

Description

This involves moving the error messages out of the notification system and into the form itself

Reminder: need to update the success and error callbacks to take in error messages as follows in `alch-edit.directive.js`:

$scope.save = function() {
var handleSave;
$scope.editMode = false;
$scope.savingMode = true;
handleSave = $scope.handleSave({ value: $scope.model });
if (handleSave !== undefined && handleSave.hasOwnProperty('then')) {
handleSave.then(
function success(data) {
$scope.savingMode = false;
},
function error(error) {
$scope.savingMode = false;
$scope.editMode = true;
}
);
}
};
----
Imported from https://trello.com/c/GFM4vsr2/182-8-nutupane-display-errors-on-a-per-field-basis_

screenshot.png (64.4 KB) Preview Walden Raines, 08/18/2014 03:26 PM

Screenshot

Related issues

Related to Bastion - Bug #7142: activation-key: red border doesn't appears on updating co... New 08/18/2014
Related to Bastion - Feature #5273: Bastion: Improve handling of success/error messages acros... Duplicate 04/21/2014

History

#1 Updated by Walden Raines almost 3 years ago

  • Related to Bug #7142: activation-key: red border doesn't appears on updating content-host limit with invalid value added

#2 Updated by Walden Raines almost 3 years ago

  • File screenshot.png added
  • Assigned To set to Walden Raines
  • Triaged set to No

We are currently doing this for our "new entity" forms but we need to add this for alch-edit fields.

#3 Updated by Walden Raines almost 3 years ago

  • Status changed from New to Assigned

#4 Updated by Walden Raines almost 3 years ago

  • Status changed from Assigned to New

I looked into this some and I believe that rewriting our error messages using ngMessages (https://docs.angularjs.org/api/ngMessages/directive/ngMessages) is the way to go. ngMessages is available in Angular 1.3, which is currently in beta, so I am moving this back to "new" status until Angular 1.3 is released.

#5 Updated by Walden Raines almost 3 years ago

  • Related to Feature #5273: Bastion: Improve handling of success/error messages across parent/child $states added

#6 Updated by Eric Helms over 2 years ago

  • Triaged changed from No to Yes

#7 Updated by Eric Helms almost 2 years ago

  • Project changed from Katello to Bastion

#8 Updated by Eric Helms over 1 year ago

  • Release set to Backlog

#9 Updated by Walden Raines 6 months ago

  • Target version set to Team Tom - backlog

Also available in: Atom PDF