Conversation
|
The tests are failing, but I'm not sure it has something to do with the PR itself. |
|
This is actually not working that great because it relies on the assumption that |
|
I still will need to find time to look more closely at what this is doing. In the meanwhile, one question for context: is this the same as or similar to this workaround that I have downstream? In essence, there I found that the WB_WDI source does not really implement the SDMX-REST API per the standard. I responded by directly accessing a URL from their documentation. Is this PR similar in trying to handle a certain documented/known non-standard API behaviour? If so it will be important to have (or reference) a clear statement of what that behaviour is. |
|
@khaeru It seems indeed to be the same thing for codelists as the link you pointed at. I think the |
Add WDI dataflow/codelist/datastructure.
However, it uses a lot of unconventional quirks, which I would be happy to correct.
PR checklist