You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 17, 2020. It is now read-only.
In the near future, the API will begin using the following new properties:
next-hour-forecast-status
unavailable
temporarily-unavailable
partially-unavailable
station-offline
station-incomplete
Add support for these properties to Dutch. (Information is available in the README, and examples are visible in /lib/lang/en.js and /test_cases/en.js.)
Hi,
On it, but It is not clear to me what this would be
"next-hour-forecast-status": "next hour forecasts are $1 due to $2",
What do the variables represent here?
The docs say 'we have information to convey about our hyperlocal next-hour forecasts' which also sounds a bit cryptic to me..
Sorry for being cryptic, we'll see what we can do about the docs. In the meantime, perhaps the best example of how these are used are in the English test cases:
"Next hour forecasts are temporarily unavailable due to all nearby radar stations being offline.":
["sentence", ["next-hour-forecast-status", "temporarily-unavailable", "station-offline"]],
"Next hour forecasts are partially unavailable due to gaps in coverage from nearby radar stations.":
["sentence", ["next-hour-forecast-status", "partially-unavailable", "station-incomplete"]],
"Next hour forecasts are unavailable due to all nearby radar stations being offline.":
["sentence", ["next-hour-forecast-status", "unavailable", "station-offline"]]
In the near future, the API will begin using the following new properties:
next-hour-forecast-status
unavailable
temporarily-unavailable
partially-unavailable
station-offline
station-incomplete
Add support for these properties to Dutch. (Information is available in the README, and examples are visible in
/lib/lang/en.js
and/test_cases/en.js
.)Tagging @realjax, @cygnus6, and @michaelarnauts if you have an opportunity to take a look!
The text was updated successfully, but these errors were encountered: