summaryrefslogtreecommitdiff
path: root/users
AgeCommit message (Collapse)Author
2012-12-18only destroy user that has been persisted in teardownAzul
2012-12-18make sure we have email_aliases at all before testing for an error on the lastAzul
2012-12-18refactored email_alias creation and validationAzul
using CouchRests user.email_aliases.build so the casted_by method is set in the alias Used this to move the validations into the alias itself. This is where they belong and allows us to render the errors inline along the email field they belong to.
2012-12-18adjusted tests - we now reload the user so invalid records are clearedAzul
Actually that might not be the best idea. Issue at hand was that invalid email aliases were getting displayed when rendering the edit form again. We probably want to solve this different.
2012-12-18display errors on email tab properlyAzul
still needs a bit of refactoring in the view
2012-12-17activate email tab after changing email settingsAzul
2012-12-17enabled destroying email aliases - no ajax yet.Azul
2012-12-17Merge branch 'feature/fixing-signup-and-login-issues'Azul
2012-12-17fixed inclusion of stub record helperAzul
2012-12-17fixed all user functional testsAzul
2012-12-13Merge branch 'master' into developAzul
Conflicts: users/test/unit/user_test.rb
2012-12-13Merge branch 'feature/email-aliases-model'Azul
2012-12-13use the same partial for Email and LocalEmailAzul
2012-12-13refactor: changed add_email to add_email_aliasAzul
that's what it does. Changed all tests to use it instead of the attributes method
2012-12-13refactor: Email constructor now takes string or hashAzul
This allows us to reuse add_email from email_aliases_attributes=
2012-12-13refactor: allow adding email aliases directlyAzul
2012-12-13ensure users do not have duplicate email aliasesAzul
nor aliases that are the same as the original email for that matter
2012-12-13LocalEmail added - will validate uniqueness amongst emails and aliasesAzul
2012-12-12find users by email and aliasesAzul
2012-12-12Merge branch 'master' into developAzul
2012-12-11make sure can login twiceAzul
2012-12-10email format validationsAzul
2012-12-10make sure client side validations also run after tabs were switchedAzul
2012-12-10use consistent naming scheme across CA, webapp and couchDB installAzul
2012-12-10created generic Email class and use it with EmailAliasesAzul
2012-12-10actually allow adding email aliasesAzul
2012-12-09basic form added to user settings, simple model createdAzul
2012-12-09first steps towards email aliasesAzul
* unit tests draft * controller draft
2012-12-08serve api version 1 in /1/Azul
Just a very simple start for now. Do we want to use the api for the secure remote password auth from js?
2012-12-07Merge branch 'master' into help_developjessib
Conflicts: app/views/layouts/application.html.haml help/app/controllers/tickets_controller.rb help/test/functional/tickets_controller_test.rb users/test/support/stub_record_helper.rb
2012-12-07fixed test to work with edit view that includes email and email forward.Azul
2012-12-07fixed signup and removed flash that was not getting displayedAzul
I also tried flash.keep(:notice) but that did not help - not sure how to keep the flash until the root url has rendered.
2012-12-07adding a bunch of translationAzul
2012-12-07first stub at displaying success messagesAzul
2012-12-07refactor: use seperate form for signupAzul
creating and editing users differ so much now it's not worth reusing the complex user_form_with for the signup.
2012-12-07using normal requests for user updates except passwordAzul
password requires ajax for secure remote password to work
2012-12-07refactored views to ease adding of email formAzul
2012-12-06forgot to add new partialAzul
2012-12-06seperated login and password changes in settingsAzul
2012-12-03refactored tests with new find_record helperAzul
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.
2012-12-03enable users to cancel their accountAzul
2012-12-03enable admin to edit usersAzul
2012-12-03make tests pass on an empty dbAzul
2012-12-01using login :is_admin => true instead of real recordsAzul
Travis CI does not seem to have the admin user records. Let's not depend on them and just stub the admin user.
2012-12-01Merge branch 'develop' into help_developAzul
2012-11-28admins can destroy usersAzul
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.
2012-11-26removing merge leftoversAzul
2012-11-26Merge branch 'develop' into help_developAzul
2012-11-26forgot the user partialAzul
2012-11-26Merge branch 'develop' into help_developjessib