submit-social-housing-lettings-and-sales-data

1442 Commits

230 Branches

287 Tags

80 MiB

Tree: c712ae3db5

Commit Graph

Author	SHA1	Message	Date
Stéphane Meny	c712ae3db5	Hides the owning organisation instead	3 years ago
J G	5eac424384	CLDC-1337-permitted-user-can-add-location-when-creating-scheme (#704 ) * added last step * not finding postcode field * testing being direct to add locations page after submitting support questions * added route to locations controller * location controller spec * location controller * added template for new * next step in feature * added postcode * added name to locations * removed total units from schemes * moved total units to locations * changed type of unit type in db * using type of units * add locations page is finished * purged total units and added test for location create * creating location * testing creating location as data provider * fixed factory * refacotred update/create and added test creating location as a coord user * testing returning back to create page if create another location is selected * testing returning back to create page if create another location is selected - part 2 * thanks rubocop * thanks rubocop * testing back from new location * returned tests back * testing clickable locations link * testing clickable locations link under correct context * correctly looking table * table with caption * wip * fixed failing exisiting tests * fixed failing exisiting tests - part 2 * validating postcode case logs style * validating postcode specs * validating postcode specs debugger removed * navigation when editing location * spike creating new location after addition * small refactoring * added test to add another location from locations page * added test to amend a location * added test to amend a location - part 2 * testing location cell * added wheelchair adaptions to the unit tyupe * rebased * testing postcode missing * testing creating schem for a different org for coordinator * testing new scheme for a different org for coordinator * upcasing all postcodes before creation * testing edge cases around postcodes and yes or no for another location * create locations with support user * details locations specs * update locations specs * rubocop * checking raising error * fixed failed test * switched yes and no for wheelchairs * routes refactoring * fixed routing - WIP * further chanegs * feature tests passing * correct page when errros * redundant page * moving viewing locations away from schemes controller * new is fixed * create fixed * fixed locations specs * fixed tab nav specs * completed location specs * lint	3 years ago
J G	7815965af1	CLDC-1290 Permitted user can create a new scheme (#671 ) * added test to find link to create a new scheme * added button to create a new scheme * testing arriving to the new scheme form * non exsiting link to controller new action * SPIKEEEE * first page complete * posting to create * refactored scheme to enums * refactored new scheme page to use enums as well * views * SPIKE WIP * SPIKE WIP * SPIKE WIP * drawing list of scheme details * expanded on feature seeing more fields to fill in * expanded on feature seeing more fields to fill in 2nd page * refactored * working back buttons * working flash * more change in wip * default value for org * working spike * some spacing * filling answers * spike finished * correct name for details * testing fill in details * removed gem and further tests * Add has other client group field to schemes. Display it in the check answers. Fix tests and routing * remove details view and path Co-authored-by: baarkerlounger <baarkerlounger@users.noreply.github.com> * WIP change update paths * Implement changing answers (except the details one) * Add details page back for editing scheme details * added missing test for support questions and nested check answers under correct context * checking the back functionality * rubo and lint * checking the back functionality for primary gourp * checking the back functionality for confirm secondary * checking the back functionality for secondary group * checking the back functionality for support answers * checking the back functionality for returning to check answers from details page * checking the back functionality for returning to check answers from primary group page * checking the back functionality for secondary group confirm yes * checking the back functionality for secondary group confirm yes - fixed * checking the back functionality for secondary group * checking the back functionality for secondary group -fixed * checking the back functionality for returning from support page * Do not display secondary client group if the scheme doesn't have one * Add details path to schemes controller update method * Add more tests for back button * Add tests for new controller method * Add tests for creating schemes as data coordinator * fixed schema * added test for missing params when creating scheme * create for support user with or withotu required param * code to get controller render errors when required param is missing * code to implement correct validation * code to implement correct validation - part 2 * highlight missing field * doing silly dance to get correct field highlighted on the error * testing patch for schemes * testing patch for schemes - correct path * small refactoring * testing primary client group update via regular path * testing primary client group update via check answers page * testing confirm secondary group update with YES NO and returning from check answers page * testing updating secondary client group update and returning from check answers page * testing support answers and returning from check answers page * testing details and returning from check answers page * weird path when no names supplied * rubocop * lost in rebasing * started id to code refactoring * model specs remastered * fixed scheme controller specs * further refactorings * fixing feature schemes * final touches * removed code from db * remaining code purged * rubocop * included check for owning org field * checking for stock owning org selection * added stock owning org * added stock owning org on new page * added stock owning org to details * removed total units * managing related schems properly via Org * managing related schems properly via Org - rubocop * small refactoring * small refactoring - 2 * small refactoring - 3 * tests for owned_schemes and managed_schemes * rubocop * added tests for support user creating scheme * rubocop -a * tests for a primary-client-group * tests for a secondary-client-group * tests for a confirm-secondary-client-group * tests for a check-answers * tests for a details * rubocop * redundant action in controller * Trigger WF * switched to int for confirm * flashing test * flashing test for support user * flashing test rubocop Co-authored-by: Kat <katrina@madetech.com> Co-authored-by: baarkerlounger <baarkerlounger@users.noreply.github.com>	3 years ago

Author

SHA1

Message

Date

Stéphane Meny

c712ae3db5

Hides the owning organisation instead

3 years ago

J G

5eac424384

CLDC-1337-permitted-user-can-add-location-when-creating-scheme (#704 )

* added last step

* not finding postcode field

* testing being direct to add locations page after submitting support questions

* added route to locations controller

* location controller spec

* location controller

* added template for new

* next step in feature

* added postcode

* added name to locations

* removed total units from schemes

* moved total units to locations

* changed type of unit type in db

* using type of units

* add locations page is finished

* purged total units and added test for location create

* creating location

* testing creating location as data provider

* fixed factory

* refacotred update/create and added test creating location as a coord user

* testing returning back to create page if create another location is selected

* testing returning back to create page if create another location is selected - part 2

* thanks rubocop

* thanks rubocop

* testing back from new location

* returned tests back

* testing clickable locations link

* testing clickable locations link under correct context

* correctly looking table

* table with caption

* wip

* fixed failing exisiting tests

* fixed failing exisiting tests - part 2

* validating postcode case logs style

* validating postcode specs

* validating postcode specs debugger removed

* navigation when editing location

* spike creating new location after addition

* small refactoring

* added test to add another location from locations page

* added test to amend a location

* added test to amend a location - part 2

* testing location cell

* added wheelchair adaptions to the unit tyupe

* rebased

* testing postcode missing

* testing creating schem for a different org for coordinator

* testing new scheme for a different org for coordinator

* upcasing all postcodes before creation

* testing edge cases around postcodes and yes or no for another location

* create locations with support user

* details locations specs

* update locations specs

* rubocop

* checking raising error

* fixed failed test

* switched yes and no for wheelchairs

* routes refactoring

* fixed routing - WIP

* further chanegs

* feature tests passing

* correct page when errros

* redundant page

* moving viewing locations away from schemes controller

* new is fixed

* create fixed

* fixed locations specs

* fixed tab nav specs

* completed location specs

* lint

3 years ago

J G

7815965af1

CLDC-1290 Permitted user can create a new scheme (#671 )

* added test to find link to create a new scheme

* added button to create a new scheme

* testing arriving to the new scheme form

* non exsiting link to controller new action

* SPIKEEEE

* first page complete

* posting to create

* refactored scheme to enums

* refactored new scheme page to use enums as well

* views

* SPIKE WIP

* SPIKE WIP

* SPIKE WIP

* drawing list of scheme details

* expanded on feature seeing more fields to fill in

* expanded on feature seeing more fields to fill in 2nd page

* refactored

* working back buttons

* working flash

* more change in wip

* default value for org

* working spike

* some spacing

* filling answers

* spike finished

* correct name for details

* testing fill in details

* removed gem and further tests

* Add has other client group field to schemes. Display it in the check answers. Fix tests and routing

* remove details view and path

Co-authored-by: baarkerlounger  <baarkerlounger@users.noreply.github.com>

* WIP change update paths

* Implement changing answers (except the details one)

* Add details page back for editing scheme details

* added missing test for support questions and nested check answers under correct context

* checking the back functionality

* rubo and lint

* checking the back functionality for primary gourp

* checking the back functionality for confirm secondary

* checking the back functionality for secondary group

* checking the back functionality for support answers

* checking the back functionality for returning to check answers from details page

* checking the back functionality for returning to check answers from primary group page

* checking the back functionality for secondary group confirm yes

* checking the back functionality for secondary group confirm yes - fixed

* checking the back functionality for secondary group

* checking the back functionality for secondary group -fixed

* checking the back functionality for returning from support page

* Do not display secondary client group if the scheme doesn't have one

* Add details path to schemes controller update method

* Add more tests for back button

* Add tests for new controller method

* Add tests for creating schemes as data coordinator

* fixed schema

* added test for missing params when creating scheme

* create for support user with or withotu required param

* code to get controller render errors when required param is missing

* code to implement correct validation

* code to implement correct validation - part 2

* highlight missing field

* doing silly dance to get correct field highlighted on the error

* testing patch for schemes

* testing patch for schemes - correct path

* small refactoring

* testing primary client group update via regular path

* testing primary client group update via check answers page

* testing confirm secondary group update with YES NO and returning from check answers page

* testing updating secondary client group update and returning from check answers page

* testing support answers and returning from check answers page

* testing details and returning from check answers page

* weird path when no names supplied

* rubocop

* lost in rebasing

* started id to code refactoring

* model specs remastered

* fixed scheme controller specs

* further refactorings

* fixing feature schemes

* final touches

* removed code from db

* remaining code purged

* rubocop

* included check for owning org field

* checking for stock owning org selection

* added stock owning org

* added stock owning org on new page

* added stock owning org to details

* removed total units

* managing related schems properly via Org

* managing related schems properly via Org - rubocop

* small refactoring

* small refactoring - 2

* small refactoring - 3

* tests for owned_schemes and managed_schemes

* rubocop

* added tests for support user creating scheme

* rubocop -a

* tests for a primary-client-group

* tests for a secondary-client-group

* tests for a confirm-secondary-client-group

* tests for a check-answers

* tests for a details

* rubocop

* redundant action in controller

* Trigger WF

* switched to int for confirm

* flashing test

* flashing test for support user

* flashing test rubocop

Co-authored-by: Kat <katrina@madetech.com>
Co-authored-by: baarkerlounger  <baarkerlounger@users.noreply.github.com>

3 years ago

3 Commits (c712ae3db5e61fb526180ead91398527ea27d29a)