* infer case_log values from schemes
* only display relevant property information questions
* Add unittype_sh column
* Display the correct number of completed sections
* fix schema and migration
* Fix test failing in CI
This test was failing due to some different between UTC and BST time as the
record from the DB comes back with a UTC timezone. Comparing the integer values
of both will ensure that both timestamps are identical and should fix the
issue in the CI where it thinks the values are different
* only run query for scheme locations size once
Co-authored-by: Dushan <dushan@madetech.com>
* extract TYPE_OF_UNIT_MAP
* lint
* Use find insted of select
Co-authored-by: Dushan Despotovic <dushan@madetech.com>
* Make tshortfall optional based on hidden tshortfall_known question
* Add test for optional
* Add test for JSON derived and dependent on false options
* Test routing
* Fix optionality
* Remove enums
* Add some convenience methods to make validations more readable
* Gender chars instead of ints
* Remove incorrect API doc info for now
* More convenience methods
* Rename label from value method
* Wrapper hbrentshortfall
* Please the cop
* fix answered questions calculation
checkbox questions were not being counted appropriately so updated the test
for the method along with the method itself
* Fix subsection status method
* change to use question completed method
Co-authored-by: Kat <katrina@madetech.com>
* Update hb question options
* add has benefits field
* derive has_benefits
* update benefit question options
* Add nocharge field
* Add rent period question and check multiple condition sets for depends_on
* update rent period answer options
* Add carehome questions and move the remaining rent questions to income and benefits section
* Reset incfreq and incref and update rent routing based on periods
* Hide total field by default
* Total charge is inferred
* We don't need to reload if we're fetching from DB anyway
* Rubocop
* Add prefixes and suffixes
* Don't count read-only questions for section status
* Add feature test for progressive enhancement
* Progressively enhance the progressive enhancement spec
* Show inferred postcode
* Filter out the answers that were not inferred
* Refactor if statement
* Add a failing test for check answers page
* Do not show the postcode known question in check answers
* WIP - fix failing test
* Display inferred check answers value if the value is not set
* update test json
* Fix a check and method name
* Extract check for hiddent in check answers from displayed to the user
Co-authored-by: MadeTech Dushan <dushan@madetech.com>
kosiakkatrina
baarkerlounger
Dushan
baarkerlounger