-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check your requirements page (with requirements summary cards) #1019
Check your requirements page (with requirements summary cards) #1019
Conversation
…ments summary cards) https://eaflood.atlassian.net/browse/WATER-4386 This branch will add summary cards to the `check` page in the returns journey to display the customer's requirements. Each box will reflect the requirements details (item, quantity etc) and link to the relevant requirement page. This will provide a quick overview for the user on the `check` page.
…ur-requirements-page-with-requirements-summary-cards
…ur-requirements-page-with-requirements-summary-cards
…ur-requirements-page-with-requirements-summary-cards
…ur-requirements-page-with-requirements-summary-cards
…ur-requirements-page-with-requirements-summary-cards
911d950
to
18867cc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got a slight tweak I think we can make. But also, we should probably have some test coverage for how requirements now get presented based on what we've added to the presenter.
Alpha function order Alpha object order
3905468
to
d6fe389
Compare
…ur-requirements-page-with-requirements-summary-cards
…ur-requirements-page-with-requirements-summary-cards
…ur-requirements-page-with-requirements-summary-cards
I have pushed the changes for - #1019 (review) I have added a map function for the requirement to extract all fields needed for the view. I will work on the other requirment fields in the session object / view in another PR. It is assumed we need to do some fetch requests to get the information for the view (requirement.purposes) so it makes sense to do that in a separate PR. |
…ur-requirements-page-with-requirements-summary-cards
…ur-requirements-page-with-requirements-summary-cards
…ur-requirements-page-with-requirements-summary-cards
Due to the estimated complexity of adding fetch services for purposes, points and other display items. We have broken down the complex display items into their own branches of work. https://eaflood.atlassian.net/browse/WATER-4386 This branch will add purposes to the return requirement summary card Previous work done here - #1019
Due to the estimated complexity of adding fetch services for purposes, points and other display items. We have broken down the complex display items into their own branches of work. https://eaflood.atlassian.net/browse/WATER-4386 This branch will add purposes to the return requirement summary card Previous work done here - #1019
Due to the estimated complexity of adding fetch services for purposes, points and other display items. We have broken down the complex display items into their own branches of work. https://eaflood.atlassian.net/browse/WATER-4386 This branch will add points to the return requirement summary card. Previous work done here - #1019
* Check your requirements - purposes Due to the estimated complexity of adding fetch services for purposes, points and other display items. We have broken down the complex display items into their own branches of work. https://eaflood.atlassian.net/browse/WATER-4386 This branch will add purposes to the return requirement summary card Previous work done here - #1019
Due to the estimated complexity of adding fetch services for purposes, points and other display items. We have broken down the complex display items into their own branches of work. https://eaflood.atlassian.net/browse/WATER-4386 This branch will add points to the return requirement summary card. Previous work done here - #1019
* Feature returns required points Due to the estimated complexity of adding fetch services for purposes, points and other display items. We have broken down the complex display items into their own branches of work. https://eaflood.atlassian.net/browse/WATER-4386 This branch will add points to the return requirement summary card. Previous work done here - #1019
Due to the estimated complexity of adding fetch services for purposes, points and other display items. We have broken down the complex display items into their own branches of work. https://eaflood.atlassian.net/browse/WATER-4386 This branch will add returns cycles to the return requirement summary card. As of this commit there is only 'summer' and 'winter and all year' returns cycles Previous work done here - #1019
Due to the estimated complexity of adding fetch services for purposes, points and other display items. We have broken down the complex display items into their own branches of work. https://eaflood.atlassian.net/browse/WATER-4386 This branch will add agreement exceptions to the return requirement summary card. This will be a comma seperated list in the oxford comma style. Previous work done here - #1019
) * Add the returns cycle text to the returns requirements check page Due to the estimated complexity of adding fetch services for purposes, points and other display items. We have broken down the complex display items into their own branches of work. https://eaflood.atlassian.net/browse/WATER-4386 This branch will add returns cycles to the return requirement summary card. As of this commit there is only 'summer' and 'winter and all year' returns cycles Previous work done here - #1019 * chore: pre pr fixes * fix: test failing missing returns cycle assert * chore: alpha order * Update app/presenters/return-requirements/check/returns-requirements.presenter.js Co-authored-by: Alan Cruikshanks <[email protected]> * Update test/presenters/return-requirements/check/returns-requirements.presenter.test.js Co-authored-by: Alan Cruikshanks <[email protected]> * fix: use ternary for returns cycle assume that if the return is not summer it is winter as there are only two options --------- Co-authored-by: Alan Cruikshanks <[email protected]>
…age (#1076) * Add the agreement exceptions text to the returns requirements check page Due to the estimated complexity of adding fetch services for purposes, points and other display items. We have broken down the complex display items into their own branches of work. https://eaflood.atlassian.net/browse/WATER-4386 This branch will add agreement exceptions to the return requirement summary card. This will be a comma seperated list in the oxford comma style. Previous work done here - #1019 Co-authored-by: Alan Cruikshanks <[email protected]>
https://eaflood.atlassian.net/browse/WATER-4386
This branch will add summary cards to the
check
page in the returns journey to display the customer's requirements.Each box will reflect the requirements details (item, quantity etc) and link to the relevant requirement page.
This will provide a quick overview for the user on the
check
page.