summaryrefslogtreecommitdiff
path: root/users
AgeCommit message (Collapse)Author
2013-01-15minor: put emails in unstyled ul and simplifyAzul
Just found out that render(@collection) returns nil for emtpy collections. So that is usefull for putting messages about the emtpy collection in an or clause.
2013-01-14Use partials for displaying details shown when viewing a user. Some of these ↵jessib
partials have specific CSS for another use, so we will likely want to tweak this.
2013-01-14Merge branch 'master' into feature/show_user. Added new tests.jessib
Conflicts: users/test/functional/users_controller_test.rb
2013-01-14minor: further cleanup - try to leave no record behindAzul
2013-01-14tickets controller tests passingAzul
2013-01-14got users controller test to pass - tickets controller test next.Azul
2013-01-11basic dummy data for usersAzul
2013-01-10Add test for showing user.jessib
2013-01-08Adding show view for users.jessib
2013-01-06views only emit 1 as value now, doc can be includedAzul
2012-12-22moving the js for view definitions into separate filesAzul
This way we get syntax highlighting and so on.
2012-12-22Merge pull request #7 from leapcode/feature/validate-email-domainazul
validating email domain and displaying it as the placeholder
2012-12-20render proper tab on updateAzul
2012-12-20fixed tests, testing corner cases, fixed theseAzul
2012-12-20this is what += is there forAzul
2012-12-20validating email domain and displaying it as the placeholderAzul
This even works client side. :)
2012-12-18refactor: using tab partials for user editingAzul
2012-12-18adopted functional tests to new controller designAzul
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.