Add friendly formatting to two-part tariff endpoint #344
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 update our two-part tariff endpoint to ouput data in a friendlier format, optionally allowing us to view the raw data if specified.
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-4046
We update our two-part tariff endpoint to output data in a friendlier format, optionally allowing us to view the raw data if specified.
The endpoint is still
/check/two-part/{region}but it now takes an optional/{format}path parameter, eg/check/two-part/1/raw. We default tofriendlyoutput if nothing is specified, which is currently a simple{ "hello": "world" }response but will ultimately be in a format similar to the UI.rawformat simply shows the end result of the db queries and matching without any further changes. Any other format value returns an error response.