baarkerlounger/submit-social-housing-lettings-and-sales-data - submit-social-housing-lettings-and-sales-data - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Manny Dinssa	ec55d405e1	CLDC-3618: Support user - View bulk uploads page (#2666 )	3 months ago
Manny Dinssa	c7bf7a037d	CLDC-2588-Separate soft and hard validation errors in bulk upload (#2545 ) * Separate soft and hard validation errors in bulk upload	5 months ago
kosiakkatrina	d87d6a7fb3	Update node version from ^16.0.0 to ^18.0.0 and ruby 3.1.2 to 3.1.4 (#1794 ) * Update govuk-prototype-components * Update node version * Udate versions in the pipeline * Do not fix to a specific buildpack version * Update ruby version * Upgrade govuk-frontend * Update summary cards to use govuk frontend component	1 year ago
Phil Lee	903cf81749	CLDC-2305 Bulk upload setup fields validations (#1633 ) # Context - https://digital.dclg.gov.uk/jira/browse/CLDC-2305 - This is rework to add missing validations for sales setup fields for bulk upload # Changes - There is code that clears log fields if they are not a valid option. in order to generate errors for these we check certain fields for content prior to `log.valid?` being called. Unfortunately there does not appear to be an easy way to access to valid options therefore these values have been hard coded - Privacy notice must be accepted other considered a setup error - The `type` question can actually be one of three questions with the same identifier. these are excluded as part of `validate_valid_radio_option` and instead validated with a different mechanism. The rationale being that `log.valid?` will clear data before we get there - Remove tests associated to upload threshold which are no longer required	2 years ago
Phil Lee	210a25eaf5	fix bulk upload summary error ordering (#1562 )	2 years ago
Phil Lee	af53a9f0df	CLDC-2184 Fix ordering for bulk upload errors by cell (#1544 ) # Context - https://digital.dclg.gov.uk/jira/browse/CLDC-2184 - bulk upload error reports were not sorting by cells correctly # Changes - there was an issue where `Z100` would come after `AA100` which is not correct - fix ordering issue above - also made change so this is now delegated to the database rather than sorting in ruby	2 years ago