leap_web.git/users/test/functional/v1, branch master [leap_web] moving users: app and test files 2014-04-08T09:49:14+00:00 Azul azul@leap.se 2014-04-08T09:49:14+00:00 b6d14dc19dd350a807826e3e097738a36613e083 






rename authorize to require_login
2014-02-10T13:26:30+00:00

Azul
azul@leap.se

2014-02-07T13:38:56+00:00

3f9dc65636afb57fed441978dca4bf7d3209bd2d

authorize_admin -> require_admin

also add require_token which will ensure token has been used for auth.





authorize_admin -> require_admin

also add require_token which will ensure token has been used for auth.







Some refactoring, to simplify user model, optimize, and allow messages to be sorted by date (although are not now.)
2014-01-07T20:57:01+00:00

jessib
jessib@riseup.net

2014-01-07T20:57:01+00:00

c7e66852324714a166dd35dc3d5873a0053dcb9b

Also, rather than use whenever gem, will have cron job created to call task.





Also, rather than use whenever gem, will have cron job created to call task.







Add authentication to API, but not sure it is best way.
2013-12-31T20:16:43+00:00

jessib
jessib@riseup.net

2013-12-31T20:16:43+00:00

47d9b62913789358aefe769de6b7e33da8547891












Cleanup of code for messages API and cron job for 1 month payment warning. Authentication still remaining piece.
2013-12-31T19:48:18+00:00

jessib
jessib@riseup.net

2013-12-31T19:48:18+00:00

f9c96f8844205afe3c310b5b914752068728d38f












Change structure to be more no-sql-y, rather than relational.
2013-12-30T23:22:44+00:00

jessib
jessib@riseup.net

2013-12-30T23:22:44+00:00

16b28882aa7659fb89e1661ed8af0c0db72642c8












Catching some corner cases & new tests.
2013-12-24T21:27:22+00:00

jessib
jessib@riseup.net

2013-12-24T21:27:22+00:00

7f12c795207ac818bffac42aa581bf1165f9e424












Add API tests and some refactoring of messages so we can get a user's messages within the webapp.
2013-12-24T20:36:42+00:00

jessib
jessib@riseup.net

2013-12-24T20:23:04+00:00

e4390e2ee5b2df20038f12865db462cf1e208ee6












test helper to expect_logout.
2013-10-30T19:17:43+00:00

Azul
azul@leap.se

2013-10-30T19:13:16+00:00

f6924bfe3b540c384fa53e55db9db3a64a34ced3

Currently it expects both the session and the token to be cleared. This might change. But we'll always have a definition of what it means to logout we can test this way.





Currently it expects both the session and the token to be cleared. This might change. But we'll always have a definition of what it means to logout we can test this way.







Account: Composition to handle User and its identities
2013-09-03T06:54:25+00:00

Azul
azul@leap.se

2013-08-30T09:20:04+00:00

859b79d0dcd53c85bb57e3db888a1af702802987

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).





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).