leap_web.git/test/integration/api, branch drop/ruby-2.1

fix: respond with error on invalid pgp key

2017-11-16T12:18:55+00:00

We used to just ignore the key.
Also separated the code for handling key updates from other
user updates. This should eventually be moved to a different
route. Mixing the two makes the implementation really hard.

fix: sanity checks on user params

2017-10-24T11:33:03+00:00

fixes #8801

Includes a test reproducing 500 on lynx

We now make use of ActionController::Parameters require and permit
methods.

use i18n for login test

2017-08-15T18:31:04+00:00

bugfix: handle couch 404s

2017-03-23T08:49:17+00:00

our special error handler for json requests would turn all exceptions
into 500s - removed it. now the rescue_responses can do their thing
again.

Adds recovery code to user account

2017-03-10T14:28:39+00:00

Related with https://github.com/pixelated/pixelated-user-agent/issues/924
With @aarni

respond_to on a per controller basis

2016-08-19T09:15:31+00:00

If you inherit respond to and call it again in your controller
it will not overwrite the previous but add to it.

Since we always have some exceptions from the rules it's probably
easiest to be explicit in the controllers that require it themselves.

[feature] restrict is_admin in the user api, to only allow querying

2016-07-14T13:45:09+00:00

for him/herself

So that it we do not expose the is_admin property to anyone else
including other admins.

Merge branch 'develop' of https://github.com/leapcode/leap_web into feature/expose_admin_in_api

2016-07-14T13:44:07+00:00

[feature] expose is_admin in the user api

2016-06-22T17:17:15+00:00

So that whoever consumes the API can use this attribute to
determine if admin functionalities should be made available to
the current user.

api: allow version bumping - bump to 2

2016-05-18T18:07:41+00:00