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

Issues and Downtime Feature #66

Merged
merged 121 commits into from
Feb 4, 2016

Conversation

jsavell
Copy link
Contributor

@jsavell jsavell commented Dec 21, 2015

The Issues tab (added in the Resources module and updated in the Organizations module) includes two new features:

  1.  Issues/Problems with a resource can now be reported through CORAL for the purpose of tracking. An alert can be set up so that the user receives a reminder to follow-up on the problem. Once the issue has been addressed, it can be archived and a list of all open and archived issues can be viewed and/or exported.
    
  2.  Current and upcoming downtime can also now be tracked in CORAL. As with the issues, a list of current/upcoming and previous downtime can be viewed and/or exported.
    

@@ -185,6 +185,12 @@ function getCheckboxValue(field){
}
}

function validateEmail(email) {
Copy link
Contributor

Choose a reason for hiding this comment

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

use type="email" (HTML5) instead of a js validation

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We're using this function in two places in https://github.com/TAMULib/CORAL-Resources/blob/issues_feature_remastered/js/resource.js In the first, it's in a non-submitting context, so HTML5 validation isn't useful (L.187).

In the other (L.161), it's as part of the usual Coral way of pushing error messages to nearby spans to notify users of what they need to fix. If we rely on browser validation for this one part, it means the user has to look in more than one place and for more than one style of error feedback.

The alternative is refactoring the error checking to rely on the JS validation API and HTML5 'required', but no other validation in Coral uses this that I'm aware of, so that seems more like a module wide feature beyond the scope of the Issues/Downtime feature.

Also, the actual email validation regex is the same and in some cases, stricter, than what the browsers themselves are using.

doug-hahn added a commit that referenced this pull request Feb 4, 2016
@doug-hahn doug-hahn merged commit 2c03c25 into ndlibersa:master Feb 4, 2016
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.

4 participants