added-env-based-history-window #660
Open
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.
Pull Request
Description
This PR introduces a configurable history window for the Quartz Frontend via environment variables.
It allows developers to control how far back in time the UI fetches solar forecast and actual data — without changing code manually.
Previously, the application used a fixed time window (e.g., 48 hours).
Now, this can be configured using environment variables such as:
NEXT_PUBLIC_HISTORY_WINDOW_TYPE=fixed|rolling
NEXT_PUBLIC_HISTORY_WINDOW_HOURS=48|72
Fixes #655 — Set start of window for UI for all forecast/actuals
How Has This Been Tested?
Ran the application locally using different environment variable settings:
NEXT_PUBLIC_HISTORY_WINDOW_TYPE=fixed
NEXT_PUBLIC_HISTORY_WINDOW_TYPE=rolling
Verified that the API requests (to
/v0/solar/GB/gsp/pvlive/alland/v0/solar/GB/national/forecast) reflected correctstart_datetime_utcandend_datetime_utcparameters.Confirmed that the charts updated accordingly for both 48-hour and 72-hour modes.
Ran
yarn lintandyarn testsuccessfully after correcting formatting issues.Checklist