Commit message (Collapse) | Author | Age | Lines | |
---|---|---|---|---|
* | Use since_event_id to restrict query, not just data displayed. | Louise Crow | 2014-08-11 | -1/+10 |
| | | | | | Allow the same params (since_event_id, since_date) for both formats. There doesn't seem to be a particular reason not to treat them the same. | |||
* | whitespace | lizconlan | 2014-07-28 | -436/+434 |
| | | | | includes various code layout fixes | |||
* | Sending an invalid state value to add_correspondence now aborts the entire ↵ | lizconlan | 2014-07-28 | -29/+40 |
| | | | | operation | |||
* | Refactor state update API, better error handling | lizconlan | 2014-07-28 | -10/+12 |
| | | | | Filters; more 403s, fewer 500s; added logging; less duplication | |||
* | Extend add_correspondence API method to optionally accept a state param | lizconlan | 2014-07-28 | -79/+135 |
| | ||||
* | New API method for updating request state | lizconlan | 2014-07-28 | -277/+357 |
| | ||||
* | Merge branch 'hotfix/0.16.0.6' into rails-3-develop | Louise Crow | 2014-01-28 | -0/+12 |
|\ | ||||
| * | Handle a request with no user in the show request function0.16.0.5hotfix/0.16.0.5 | Louise Crow | 2014-01-28 | -0/+12 |
| | | ||||
* | | Tighten up expectation, make expected files consistent. | Louise Crow | 2014-01-17 | -12/+0 |
|/ | | | | | | | Just expecting the parsed file to include the expected one would mean success in the case where nothing has been folded. Tighten up the expectation, and add quoting placeholders to expected files that didn't have them. | |||
* | Set the calculated state on external requests. | Louise Crow | 2013-08-15 | -0/+3 |
| | | | | Set to 'waiting_response' on creation, to match the displayed state. | |||
* | Switch to just loading fixtures in tests as binary strings | Mark Longair | 2013-05-16 | -1/+1 |
| | | | | | | | | | | The data loaded with load_file_fixture is generally used in the tests as if it were binary data received from the MTA, so just load it as binary data - in Ruby 1.9 this means that it will end up with the encoding ASCII-8BIT. The same is the case when reading data from a fixture file in receive_incoming_mail. | |||
* | Spec is deprecated in favour of RSpec | Henare Degan | 2013-02-14 | -1/+1 |
| | ||||
* | Use preceding slash on paths to fixtures files | Matthew Landauer | 2013-01-28 | -2/+2 |
| | ||||
* | No need to specify extension when testing particular template is rendered | Matthew Landauer | 2013-01-04 | -2/+2 |
| | ||||
* | response.status now returns an integer | Matthew Landauer | 2013-01-04 | -5/+5 |
| | ||||
* | Add option to load_file_fixture to specify that the file contents should ↵ | Louise Crow | 2012-12-04 | -2/+1 |
| | | | | just be loaded as binary. | |||
* | The absence of an API key in an API request should be a permission denied ↵ | Louise Crow | 2012-12-03 | -6/+19 |
| | | | | error, so that notification emails don't get sent. | |||
* | Make regex for space normalization more unambiguous - it's the spaces at the ↵ | Louise Crow | 2012-11-29 | -55/+55 |
| | | | | beginning and end of the whole string that we want to strip entirely, not at the beginning and end of each line (interpretation of ^ and $ is subject to default multiline behaviour of the regexp interpreter) | |||
* | add magic encoding comment to specs | James McKinney | 2012-10-10 | -1/+2 |
| | ||||
* | Add a since_date parameter to the API feed | Robin Houston | 2012-09-10 | -0/+15 |
| | ||||
* | Update other tests | Robin Houston | 2012-09-07 | -20/+25 |
| | | | | Update the other API tests to take account of the changed error behaviour. | |||
* | API errors should be JSON | Robin Houston | 2012-09-04 | -0/+32 |
| | | | | | | | | | | The API was returning Rails (HTML) errors for certain error conditions, which is inconvenient because it makes it difficult for the client to extract the error message. This patch changes add_correspondence to return JSON errors (still with suitable HTTP status codes) for two common exceptional conditions, and adds tests. | |||
* | 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! |