Chris Hill-Scott 5fda35c89d Make it clear that client do not use __init__ ...

The clients never get passed useful values to their `__init__` methods.
Rather the real values are passed through later using the `init_app`
method.

So it should be an error if the client is relying on the values that
get passed to it’s init method. Easiest way to ensure this is by making
the `__init__` method not expect any arguments and passing fake values
to the `Super` call.

2016-09-12 12:18:19 +01:00

..

__init__.py

Make _attach_current_user a pure function

2016-08-11 17:07:55 +01:00

api_key_api_client.py

Make it clear that client do not use __init__

2016-09-12 12:18:19 +01:00

events_api_client.py

Make it clear that client do not use __init__

2016-09-12 12:18:19 +01:00

invite_api_client.py

Make it clear that client do not use __init__

2016-09-12 12:18:19 +01:00

job_api_client.py

Make it clear that client do not use __init__

2016-09-12 12:18:19 +01:00

models.py

Updated flask-login to version 0.3.2

2016-05-04 14:06:14 +01:00

notification_api_client.py

Make it clear that client do not use __init__

2016-09-12 12:18:19 +01:00

organisations_client.py

Make it clear that client do not use __init__

2016-09-12 12:18:19 +01:00

provider_client.py

Make it clear that client do not use __init__

2016-09-12 12:18:19 +01:00

service_api_client.py

Make it clear that client do not use __init__

2016-09-12 12:18:19 +01:00

status_api_client.py

Make it clear that client do not use __init__

2016-09-12 12:18:19 +01:00

template_statistics_api_client.py

Make it clear that client do not use __init__

2016-09-12 12:18:19 +01:00

user_api_client.py

Make it clear that client do not use __init__

2016-09-12 12:18:19 +01:00