For some reason the result is not updated in the Spec correctly.

Should allows the client to specify the page size (may wish to change this based on type of client: mobile, desktop, etc)

Set up REST framework browsable REST API

Wierdly i put the attempt to confirm before any checks on the password. So if the passwords entered were invalid it would still expire the key. I have changed the order of this but need to confirm it and change the unit tests for this view.

Define the functionality of this controller, write a URL routing scheme for the Auth section of the app and implement the controller. Should produce a self contained subsection of the app related to user profile management.

This should work the same way as an EmailConfirmation: A time of creation will be used to check if a subscription is out of date or not.

Need to define a way of registering users to the app via the REST API. Users should be readable and creatable (NOT DELETABLE). This will map to registering and logging in.

Will need this to start making decisions about redirects in controllers etc.

Will avoid hashbangs on compatible browsers, falling back to hashbangs when necessary. See docs for details.

Navbar dropdown not working correctly when screen is compressed.

Tests should be written first.

Allow basic text searching on questions. Should also allow a topic and subtopic to be specified to narrow the search.

Should be nicer for users.

This should consist of the following:

• High level description
• Libraries used and how they fir together
• Plan to manage subscriptions: create a 'hook' for logic to check a users payment method later.
• User groups, one for free users and one for restricted
• Adding a 'restricted' boolean to questions to allow a free subset of questions to be shown to new users,

Need to check that reusing a key is not possible if it has already been used successfully.

Think I left this out: wouldnt show up in Unit tests. Need to add tests to make sure requests are made with this as well.

This is obviously impossible to do as the users email must be confirmed first.

Remove all references to user groups within code and seperate this out into app level settings

Check that cookie is saved and deleted correctly.

This will serve as a basis for all the other question views, such as by topic, subtopic, etc as these just provide different parameters via the url to the controller.

Try and mimics style used by DJR: having all properties in a dictionary under an app name and a module which accessess this.

Should additionally make any require changes to the formatting of the emails

I think this will be a cleaner solution and cut out possible Javascript scoping errors.

WIll involve going through controllers ad-hoc and adding in alerts, etc to help user interaction.

Havent tested this feature. Need to add tests for it.

To be done once all auth partials are integrated correctly.

Can log in and return the token successfully but it appears that views which require the permissions.isAuthenticated permission to be satisfied raise a 401 UNAUTHORIZED. Implies a problem with the token.

Emails wont actually work at the moment. Want to change this for testing.

Want to add some suitable validator for checking passwords. Will need to define suitable criteria first.

Users should register for a basic account by entering the following data:

• Username (unique)
• Email (unique)
• First Name
• Last Name

The email should be verified by sending an email to the user which gives them a verification token. Once the email has been verified, the user can log on. The following requirements must be met for email verification:

• The verification email link should time out after a configurable time in days, after which the link is no longer valid.
• There should be a way, presumably via a ModelManager, to detect completed, outstanding and expired confirmation codes so correct action can be taken on them. Additionally it may be useful to have a 'Delete expired confirmations' feature added to the admin page.
• The email content and header should be configurable.

Will probably use WebStorm. Should help by automating a lot of the nonsense.

Have added this for development. It must be disabled before deployment. Do so by uninstalling the django-cors python package

Relies of pagination being addedd.

Cant find a way to do this. It can be done using $scope, but I dont want this.

Tests wont run and I dont know why. Need to fix this.

Can avoid the need for a broadcast events by having a service handle alerts to the user. Can simply have controllers pull these off or store them for the user to read.

Otherwise its possible to do things like submit an update to your user profile without being logged on yet.

Returning promises is much more in line with the way Angular works (the controller using it wont be blocked). Will have to change test code as well to check the status, etc that is returned as part of the response to the promise. This should not be diffcult.

Djoser has an example of this in its root view, look at this for help.
Should have one for authentication and one for questions.

Envisage this working as follows:

1. When the user logs in, create a cookie with a certain time limit.
2. When the app starts, check for the presence of this cookie and if its there, then take the info from it.
3. Delete the cookie if the user logs out.

At some point the decision will be made between whether or not we wish to charge a subscription or have a free sponsored site. Whichever this is, I will need to sort out the user groups to either remove them or establish the following if we opt for subscriptions:

• Regular users should be assigned to the 'Bronze' User group. This means they must be assigned this group by a custom serializer when they register
• Paid users must be added to the silver group, and taken away from this group when they're subscription expires.