leap_web.git/users/app/models, branch 0.2.3

user.account shortcut to Account.new(user)

2013-09-18T08:27:19+00:00

Merge pull request #73 from azul/bugfix/3623-teardown-test-data-properly

2013-09-03T17:48:13+00:00

Bugfix/3623 teardown test data properly

Account: Composition to handle User and its identities

2013-09-03T06:54:25+00:00

We have a lot of things that act upon a user record and one or more of it's identities at the same time:
* Sing up: Create a user and it's initial identity
* Rename:  Change the username and create a new identity, turn old into an alias
* Cancel Account: Remove user and all their identities.

In order to keep the User and Identity behaviour isolated but still have a this logic represented in a sinle place the Account model deals with all these things.

We could have overwritten the User#create, User#update and User#destroy methods instead. But then we would always create identities, even if we only need a user (for example in tests).

expire token according to config setting auth:token_expires_after

2013-09-03T06:36:17+00:00

there's no need for User#find_by_param. clean it up

2013-08-30T12:54:30+00:00

token.user will get you the right user

2013-08-27T12:57:44+00:00

This way we can stub the token to return the user directly. Stubbing User.find_by_param is not a good idea as it will make all calls to User#find_by_param with a different id fail.

use the same login validations on sessions and users

2013-08-21T07:49:26+00:00

The session ones were outdated so valid usernames could not login if they contained a '.'

Refactored so both models use the same module for this validation to ensure consistency.

Tweak to parameters to fix wrong-number-of-arguments error blocking other work.

2013-08-20T19:37:58+00:00

keeping the pgp_key accessors for User so views still work

2013-07-24T09:38:32+00:00

separate signup and settings service objects for user

2013-07-24T08:56:45+00:00