-
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
Create Completed Monthly Return Logs page #1484
Draft
StuAA78
wants to merge
16
commits into
main
Choose a base branch
from
new-view-completed-monthly-return-logs-page
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
+540
−6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We create an initial route, controller and service, which work together to pull the data via a legacy API request. This is then sent to an initial page which simply dumps the data to the page.
We've found that the purpose text we retrieve is all-caps and we want it to be in title case. However `BasePresenter.titleCase()` does not handle this -- it capitalises the first letter of each word while leaving the rest of the word as-is, effectively returning the same all-caps string. Up until now this behaviour was neither desired nor undesired; we simply didn't have a need to convert an all-caps string to title case. Now that we do, we amend `BasePresenter.titleCase()` to first convert the string to lower case before capitalising the first letter of each word, thus forcing all-caps text into title case.
This follows our convention (followed most of the time!) of starting with the resource name i.e. what we called the model! Then, the main route (show all records) is `index.*.js`/`index.njk` and for an individual it is `view.*.js`/`view.njk` Co-authored-by: Stuart Adair <[email protected]>
This gives an initial starting example for how we can grab the data we need for the view without needing to make a request to the legacy service or parse its response.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://eaflood.atlassian.net/browse/WATER-4745
https://wrls-prototype.herokuapp.com/sandbox/licence/returns-current/return