alaveteli - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Lines
*	JSON new events feed	Robin Houston	2012-07-04	-1/+39
\|
*	Atom feed of request events	Robin Houston	2012-07-04	-0/+16
\| \| \| \| \| \| \| \| \| \|	We need not only new requests, but new outgoing correspondence of any sort. The idea is that this feed will contain any event that would have triggered an email to be sent to the public body, so can be used as an alternative, equivalent way to stay up-to-date with happenings on WDTK (or the Alaveteli installation of choice).
*	API controller tests all pass	Robin Houston	2012-06-18	-3/+15
\|
*	WIP attachment uploading via API	Robin Houston	2012-06-06	-4/+20
\|
*	Test for attaching a file via the API	Robin Houston	2012-06-06	-0/+36
\| \| \| \|	Not yet implemented, so the test fails.
*	Correct comment\	Robin Houston	2012-06-06	-1/+1
\|
*	Use a fixture for the external request	Robin Houston	2012-06-06	-4/+8
\|
*	API: Some testing of show_request	Robin Houston	2012-06-06	-0/+13
\|
*	API: test also for refusal conditions	Robin Houston	2012-06-06	-0/+39
\| \| \| \| \| \|	The API must not allow people to update requests that they shouldn’t, i.e. only requests that were created by the same public body, using the API, can be added to using the API.
*	API: add followup to request	Robin Houston	2012-06-06	-13/+61
\| \| \| \|	You can add a followup to a request using the API.
*	API: we can add a response to a request	Robin Houston	2012-06-06	-0/+60
\|
*	API create_request method is working	Robin Houston	2012-06-06	-1/+2
\| \| \| \| \| \|	"when using the API", it "should create a new request from a POST", AND IT DOES!
*	Fix test and fixtures so they only fail due to missing business logic ↵	Seb Bacon	2012-06-06	-4/+5
\| \| \| \|	(corrected typo, added missing fixture data, etc)
*	Test for creating a new request via the API	Robin Houston	2012-06-06	-0/+33
	This is not yet implemented. Test first!