-
Notifications
You must be signed in to change notification settings - Fork 21
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
Added datasource Bank of England database #85
base: main
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## master #85 +/- ##
==========================================
- Coverage 93.10% 90.24% -2.86%
==========================================
Files 4 4
Lines 58 82 +24
==========================================
+ Hits 54 74 +20
- Misses 4 8 +4
Continue to review full report at Codecov.
|
:VPD => "Y" | ||
``` | ||
""" | ||
struct BoeOpt <: AbstractQueryOpt |
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.
Usually we use CamelCase
for modules and type names, not for fields.
Can we switch to lowercase? Like
struct BoeOpt
date_from::Date
date_to::Date
using_codes::Bool
csvf::String
vpd::Bool
end
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.
An AbstractQueryOpt is passed to the HTTP GET command with its fieldnames and values as a query.
I chose fieldnames to be consistent with the API documentation. https://www.bankofengland.co.uk/boeapps/database/Help.asp#CSV
However, I agree that lowercase is standard for fieldnames, and since the parameter names in a HTTP GET query are case-insensitive this shouldn't cause an issue. However, underscores would not be consistent with AbstractQueryOpt as I would need to change the field names to construct the query.
There was an error
|
No description provided.