aboutsummaryrefslogtreecommitdiffstats
path: root/app/views/info_request_batch
Commit message (Collapse)AuthorAgeLines
* Use new styling for batch request sent panel.Louise Crow2015-03-03-15/+54
|
* Restore missing whitespace.Louise Crow2015-03-02-1/+1
|
* Remove erroneous bracket introduced in ebf549a966a9c559bfa76b66f4ab86a75c2c1c92Louise Crow2015-01-16-1/+1
|
* Use a partial to render batch sent messageGareth Rees2015-01-13-0/+23
| | | | | | | | | | | | | | | | | | | | | | Dropped the law_used_full interpolation: So I think there are two significant bits of context here. One is that the law_used_full attribute is derived from law_used, which in turn is set on InfoRequest initialisation based on the tags applied to the public body. So different requests in a batch could have different values for law_used_full - some of them might be to bodies that only accept environmental information requests. So using the value from the batch template is not really a good proxy for the whole collection. The second is that, in any case, the distinction between the two types of request is a UK-specific feature which should be moved to the UK theme (#2085). Given these two factors, I think the cleanest thing might be to drop law_used_full from this descriptive text, and just have it say "Your requests will be sent shortly", without specifying what law will be used. – Louise Crow (@crowbot)
* Add wrapper div to make styling easier.Louise Crow2014-04-24-17/+21
|
* Only pass InfoRequestEvent to _request_listing_via_event templateLouise Crow2014-03-17-1/+1
| | | | The InfoRequest is always the one associated with the event.
* Show public body list when batch has not been sent.Louise Crow2013-12-04-9/+24
|
* Display batch requests for user on 'my requests' pageLouise Crow2013-12-04-0/+15
| | | | This is the most rudimentary possible way to give them access to the batch request urls, pending #1239
* Add a rudimentary view for an info request batch.Louise Crow2013-12-04-0/+10