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
baarkerlounger	5013869c2b	User roles (#138 ) * Users have roles * Add role to active admin * Add role to users table * Redirect organisation show to details * Remove users tab for data providers	4 years ago
Daniel Baark	c2a0ccc929	CLDC-673: Organisation Page frontend (#122 ) * Add basic info read page * Header * Better org seed * Use gem component * Tabs * Users * Users is a table rather than a summary list * Table rows * User is trackable * Date format * View component init * Add pages and routes to render * Partials * Match the prototype design * Nested layout is nicer * Except of course they're not the same width * Add button with wrong link * Add user routes * Don't move account route for now * Add component test * Rubocop * Request spec * Test views * Add a feature spec for tab switching * Move styling methods into helper * PR suggestions * PR comments	4 years ago
Daniel Baark	98e61c5746	CLDC-673: Organisation page (#114 ) * Add organisation model and user association * Add user admin panel * email * Update seeds * Update spec * Case logs belong to organisations * Org case log association * Add user case log association * User case log helper methods * Org case log relation helpers * Case log index page only shows your organisations case logs * No access to tasklist page for logs that aren't associated with your org * No access to form pages for case logs that aren't owned or managed by your org * Check answers access * Submit form access * Refactor out not found methods * Allow user admin update without password * Update feature specs * Rubocop * Update case log specs * Test admin user update without password * Spec grammar	4 years ago
Daniel Baark	7b17b38547	WIP: CLDC:680 - Refactor feature specs into smaller units (#109 ) * Refactor feature specs into smaller units * DRY spec helpers * Bump Turbo * Use database ID assignment everywhere we need ID to reduce flakiness * Update gemfile.lock * Email is unique * Selenium deprecation * Don't need let bang * Remove the uneeded extra options * Remove flaky test mitigations that didn't work * Use lockstep to remove test flakiness * Dry up condition evaluation * Spec admin user edit form * Test income refused derivation * Set valid incref * Test Case Log deletion failures * Test other household member age validations * Test all reasonable preference validation paths	4 years ago
Daniel Baark	50c50806be	Add additional tests (#108 ) * Spec case logs admin table * Spec admin user admin index * Dashboard controller panel specs * Spec panel contents * Add create specs * Don't assign non db ids if we don't need them * Fix specs for new section * Fix up fields	4 years ago
MadeTech Dushan	a0ae5025bf	Add devise gem and a first test for user login Devise is a commonly used gem for user authentication and management. Using rails generators and Devise allows us to get a lot of boilerplate code for user authentication and management and means we don't have to revinvent the wheel. Styling will need to be done for the necessary pages and there are likely to be bits of generated code that can be deleted. This will act as a starting point to be built up from using TDD.	4 years ago
MadeTech Dushan	19e2ad98cf	Add devise gem and a first test for user login Devise is a commonly used gem for user authentication and management. Using rails generators and Devise allows us to get a lot of boilerplate code for user authentication and management and means we don't have to revinvent the wheel. Styling will need to be done for the necessary pages and there are likely to be bits of generated code that can be deleted. This will act as a starting point to be built up from using TDD.	4 years ago