Age | Commit message (Collapse) | Author | |
---|---|---|---|
2013-01-18 | minor: smalles fix ever - is_admin? has a questionmark | Azul | |
2013-01-17 | Should be able to create a user when not logged in. | jessib | |
This isn't ready to merge, as there is an issue with logging in as an admin in the test. | |||
2013-01-17 | Merge branch 'master' into feature/tickets_controllers_simplification | jessib | |
Conflicts: users/app/controllers/users_controller.rb | |||
2013-01-17 | Deal with corner case where we don't have authenticated user. Will write a ↵ | jessib | |
test after merging in show view for users. | |||
2013-01-15 | For both users and tickets, if the object is not found and the current user ↵ | jessib | |
is an admin, they should see an alert that the object wasn't found, and be redirected to the current controller. If the object isn't found and the current user is not an admin, then we will continue to give an error about no access, so as not to leak information about what IDs do and don't exist. | |||
2013-01-15 | Show different ticket characteristics when viewing the users versus when ↵ | jessib | |
listing the tickets. Give a message if a user has no tickets. | |||
2013-01-15 | reverted simplification - not good to have 'none set' in a %ul | Azul | |
2013-01-15 | minor: put emails in unstyled ul and simplify | Azul | |
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-14 | Use 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-14 | Merge branch 'master' into feature/show_user. Added new tests. | jessib | |
Conflicts: users/test/functional/users_controller_test.rb | |||
2013-01-14 | minor: further cleanup - try to leave no record behind | Azul | |
2013-01-14 | tickets controller tests passing | Azul | |
2013-01-14 | got users controller test to pass - tickets controller test next. | Azul | |
2013-01-11 | basic dummy data for users | Azul | |
2013-01-10 | Add test for showing user. | jessib | |
2013-01-08 | Adding show view for users. | jessib | |
2013-01-06 | views only emit 1 as value now, doc can be included | Azul | |
2012-12-22 | moving the js for view definitions into separate files | Azul | |
This way we get syntax highlighting and so on. | |||
2012-12-22 | Merge pull request #7 from leapcode/feature/validate-email-domain | azul | |
validating email domain and displaying it as the placeholder | |||
2012-12-20 | render proper tab on update | Azul | |
2012-12-20 | fixed tests, testing corner cases, fixed these | Azul | |
2012-12-20 | this is what += is there for | Azul | |
2012-12-20 | validating email domain and displaying it as the placeholder | Azul | |
This even works client side. :) | |||
2012-12-18 | refactor: using tab partials for user editing | Azul | |
2012-12-18 | adopted functional tests to new controller design | Azul | |
2012-12-18 | only destroy user that has been persisted in teardown | Azul | |
2012-12-18 | make sure we have email_aliases at all before testing for an error on the last | Azul | |
2012-12-18 | refactored email_alias creation and validation | Azul | |
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-18 | adjusted tests - we now reload the user so invalid records are cleared | Azul | |
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-18 | display errors on email tab properly | Azul | |
still needs a bit of refactoring in the view | |||
2012-12-17 | activate email tab after changing email settings | Azul | |
2012-12-17 | enabled destroying email aliases - no ajax yet. | Azul | |
2012-12-17 | Merge branch 'feature/fixing-signup-and-login-issues' | Azul | |
2012-12-17 | fixed inclusion of stub record helper | Azul | |
2012-12-17 | fixed all user functional tests | Azul | |
2012-12-13 | Merge branch 'master' into develop | Azul | |
Conflicts: users/test/unit/user_test.rb | |||
2012-12-13 | Merge branch 'feature/email-aliases-model' | Azul | |
2012-12-13 | use the same partial for Email and LocalEmail | Azul | |
2012-12-13 | refactor: changed add_email to add_email_alias | Azul | |
that's what it does. Changed all tests to use it instead of the attributes method | |||
2012-12-13 | refactor: Email constructor now takes string or hash | Azul | |
This allows us to reuse add_email from email_aliases_attributes= | |||
2012-12-13 | refactor: allow adding email aliases directly | Azul | |
2012-12-13 | ensure users do not have duplicate email aliases | Azul | |
nor aliases that are the same as the original email for that matter | |||
2012-12-13 | LocalEmail added - will validate uniqueness amongst emails and aliases | Azul | |
2012-12-12 | find users by email and aliases | Azul | |
2012-12-12 | Merge branch 'master' into develop | Azul | |
2012-12-11 | make sure can login twice | Azul | |
2012-12-10 | email format validations | Azul | |
2012-12-10 | make sure client side validations also run after tabs were switched | Azul | |
2012-12-10 | use consistent naming scheme across CA, webapp and couchDB install | Azul | |
2012-12-10 | created generic Email class and use it with EmailAliases | Azul | |