* ensure the log review page has the correct links in the breadcrumbs
* ensure check your answers pages have the correct links in the breadcrumbs
* write feature tests to check that breadcrumbs have the correct links
* utilise rails url helpers
* when routing to a log show page, remove unnecessary :id call in url helper
* slight tweak of methods used to get name of an instance of the class
* Conditionally display a correct review log text
* do not allow the aswers from previous collection windows to be changed
* does not let the user navigate to questions for previous collection year logs
* Fix tests
* Add some docs
* Extract collection period check into a before_action and change path to rails route
* update the tasklist message
* Add abstract log class and sales log class
Created a parent log class for sales log and lettings log. Any bits common
to both sales and lettings can live in the parent class. As the sales log
functionality is built up any commonalities with lettings log can be extracted
into the parent log class. The sales log model is set up without a json form
and instead the form is defined in code - like the setup section of the lettings
log.
* update sales logs controller
* update lettings controller specs
* update filter method name
* update organisations controller
* use lettings method
* Add deleted tests back
* lint
Co-authored-by: Kat <katrina@madetech.com>
Co-authored-by: Kat <kosiak.katrina@gmail.com>
This renames the case_log to lettings_log as everything we've written so
far has been geared towards lettings of social housing so it makes sense to
have the name describe this. This is also a precursor to adding in stuff for
sales logs (whatever shape that takes)
Co-authored-by: James Rose <james@jbpr.net>
Arthur Campbell
Jack
kosiakkatrina
natdeanlewissoftwire
James Rose
natdeanlewissoftwire
Dushan
baarkerlounger
Paul Robert Lloyd