This issue is the household counterpart to issue #691. It is less severe than #691 since duplicates are not created.
Steps to reproduce:
Create a household with income x.
Note the household id in the URL as i.
Edit the income.
Note the household id in the URL as j.
Observe that i $\neq$ j.
Expected output
We should see i = j, i.e., the household id should not change while the user is editing the current household. A new household should be created only when the user explicitly instructs the app to do so.
When the user asks the app to create a new household, the app should:
Show them the current household id asking them to note it down for future reference.
Ask them to confirm if they want to create a new household, warning that they may lose access to their previous work.
Allow them to back to editing the current household.
I think this would be best integrated into a more comprehensive rethink and rebuild of the current calculator flow down the road. That said, it is reasonably important.
This issue is the household counterpart to issue #691. It is less severe than #691 since duplicates are not created.
Steps to reproduce:
x
.i
.j
.Observe that
i
$\neq$j
.Expected output
We should see
i = j
, i.e., the household id should not change while the user is editing the current household. A new household should be created only when the user explicitly instructs the app to do so.When the user asks the app to create a new household, the app should: