wrongly uses x-range requests when "hasCustomRangeHeader": false
The following queries do not respect the "hasCustomRangeHeader": false
settings:
-
https://dotstat-store.oecd.org/disseminate-final/rest/data/OECD.DAF,DSD_DEBT_TRANS_DDOWN@DF_DDOWN,1.0/all?dimensionAtObservation=AllDimensions with
X-Range: values=0-0
-
https://dotstat-store.oecd.org/disseminate-final/rest/availableconstraint/OECD.DAF,DSD_DEBT_TRANS_DDOWN@DF_DDOWN,1.0/........_T.?startPeriod=2020&dimensionAtObservation=AllDimensions&mode=available with
X-Range: values=0-5999
-
https://dotstat-store.oecd.org/disseminate-final/rest/availableconstraint/OECD.DAF,DSD_DEBT_TRANS_DDOWN@DF_DDOWN,1.0/body?startPeriod=2020&dimensionAtObservation=AllDimensions&mode=available
X-Range: values=0-5999
- microdata view: https://dotstat-store.oecd.org/disseminate-final/rest/data/OECD.DAF,DSD_DEBT_TRANS_DDOWN@DF_DDOWN,1.0/.AGO......GDO.DD.?startPeriod=2021&endPeriod=2021&dimensionAtObservation=AllDimensions
X-Range: values=0-5999
- create patch branch from master
- refactor api/sdmx to play with CONFIG?.member?.scope?.spaces (object)
- refactor request data call to have space id (and apply range config)
- refactor getBlankData (values=0-0)
- check viewer (DE is responsible to send to share proper information)
- create aftermath ticket (clean selector(s), module closure/CONFIG, refactor settings & annotation reconciliation, create tests of API for each request to check range header)
Edited by Jens Dossé