| Age | Commit message (Collapse) | Author |
|---|
|
Just a very simple start for now.
Do we want to use the api for the secure remote password auth from js?
|
|
|
|
I also tried flash.keep(:notice) but that did not help - not sure how to keep the flash until the root url has rendered.
|
|
|
|
|
|
creating and editing users differ so much now it's not worth reusing the complex user_form_with for the signup.
|
|
password requires ajax for secure remote password to work
|
|
|
|
|
|
|
|
find_record User will return a stubbed user record and make sure User.find_by_id(user.id) returns the same so it can be used in controllers.
|
|
|
|
|
|
|
|
I changed the permissions a little to be more consistent.
Now:
* admins can edit users
* users can destroy themselves.
There's no ui for either of them but theoretically they could. Not sure this is what we want though.
|
|
|
|
|
|
|
|
|
|
|
|
Also added #assert_json_error to tests.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* translating error messages
* not caching login and password in js anymore
* catching non responses
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conflicts:
Gemfile.lock
|
|
|
|
|
|
|
|
also commented the sessions controller test a bit and fixed it
|
|
|
|
Conflicts:
users/app/assets/javascripts/srp
|
|
|
|
|
|
|
|
|
|
|
|
Conflicts:
Gemfile.lock
users/app/controllers/application_controller.rb
users/leap_web_users.gemspec
|
|
|
|
|
