-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
weather module, weatherbit provider doesn't use type to set the endpoint, forces user.. #2899
Comments
yeah, seems wrong to not use the "type" param which is used in other modules and specifically mentioned in the docs. openweathermap has both params too but only uses the type only when weatherEndpoint is not specified. maybe switch the usage in this module to that of openweathermap? |
yeh, i did local change to use type.. will fix to override that with the actual endpoint.. but how do you tell user specified ? cause its a default value.. in the provider
this.config.weatherEndpoint != this.defaults.weatherEndpoint |
With my PR the weatherEndpoint is only used if explicitly set in the config, and not per default. That way existing configs still function (if at all) but new users can rely on the type value to work. |
Looking at the code of other providers it seems that at least darksky should have the same problem... |
I think we shouldn't investigate in this because "The Dark Sky API and website will continue to function until March 31st, 2023". Source: https://blog.darksky.net/ |
@khassel I think u meant invest (spend energy). it's a tiny thing, for consistency sake |
thanks, yes ... |
It might be tiny, but I still would like to test it before commiting any change. So without any darksky credentials I wont be able to do it. |
send an email to my userid at gmail and I will send my key |
Thx for the key, fixed the metric stuff in my WeatherUnitCleanup-PR but somehow darksky seems ok with the "normal" config (type), can you confirm? |
yes, darksky worked with type and weatherProvider no other settings |
all in title
The text was updated successfully, but these errors were encountered: