- 23 Aug, 2014 5 commits
-
-
RawKStar77 authored
-
RawKStar77 authored
-
RawKStar77 authored
-
Randall Leeds authored
Tag Styles
-
Randall Leeds authored
-
- 22 Aug, 2014 5 commits
-
-
RawKStar77 authored
-
Randall Leeds authored
The selectors and markup here could use a cleanup, but at least now collapsed annotations that have markdown lists and things will still collapse.
-
Randall Leeds authored
-
Randall Leeds authored
Tags Redux: styling tags
-
Jake & Randall authored
-
- 21 Aug, 2014 30 commits
-
-
RawKStar77 authored
-
Randall Leeds authored
-
Randall Leeds authored
Account Management
-
Randall Leeds authored
-
Randall Leeds authored
Otherwise, this only clears at the appropriate time when triggered by a scope change, not when triggered by keyup.
-
Randall Leeds authored
-
Randall Leeds authored
The form-input class now has the directive responsible for setting the error classes. It watches its scope and sets the errors only if the model is defined or pristine. This guard keeps the error class from being set until validation passes (when the model becomes defined) and keeps it from being cleared until the pristine state is reset. The form-validate directive is now just a controller for form-input to register with. It sets all fields to dirty and forces a render on submit. These mechanisms are better all around than trying to listen for a the model to be undefined and setting pristine automatically. The model is undefined whenever validation is failing. There are times when the from should maybe be cleared but still show errors. Now, it is left up to other code to set pristine if the form should be reset.
-
Aron Carroll authored
The $setViewValue field wasn't working.
-
Aron Carroll authored
This fixes an issue where logging in, then logging out and opening the login form will reveal a form with error messages. This is due to the execution order of events post login. https://github.com/hypothesis/h/pull/1275#issuecomment-51777983
-
Randall Leeds authored
-
Aron Carroll authored
-
Aron Carroll authored
-
Aron Carroll authored
-
Aron Carroll authored
-
Aron Carroll authored
-
Aron Carroll authored
Now all forms use the profile view name plus "form". For example the form for the edit_profile view would be editProfileForm. Each ngModel is namespaced on the scope by the form name. So again this would be $scope.editProfile. Lastly each field name uses the corresponding field in the request payload. All fields are camel case. This should make it far easier in future to read a form and match it to the http request.
-
Aron Carroll authored
-
Aron Carroll authored
-
Aron Carroll authored
-
Aron Carroll authored
Moved the event handling logic into the AccountManagement controller
-
Aron Carroll authored
Also moved the code out of the directives module and into it's own file.
-
Aron Carroll authored
-
Aron Carroll authored
-
Aron Carroll authored
-
gergely-ujvari authored
-
gergely-ujvari authored
As a first step for user deletion we just deactivate the user. In the backend the ProfileController class has a new method disable_user which (if the correct password is given) deactivates the user In the backend the session/profile factory has a disable_user action with which the ProfileController can be reached.
-
Aron Carroll authored
-
Aron Carroll authored
We now just listen for changes to the form.$error object rather than having the controller triggering an error event. This now supports other changes such as external directives adding validations to inputs also.
-
Aron Carroll authored
We're only implementing the account form for the moment.
-
Aron Carroll authored
This now directly inlines the template instead of using the Angular templates. This keeps it consistent with the login tabs. It also replaces the panels implementation with the Angular tabbable directive.
-