plasmoid-wunderground-extended
plasmoid-wunderground-extended copied to clipboard
rliwoch
[Feature Request] Allow wunderground API key to be configurable
Is your feature request related to a problem? Please describe. ~~I can't confirm but I suspect that~~ all users of this widget are using the same API key as it is not a configurable option.
I just setup and registered my own PWS and installed this widget to get real-time data from it. My widget is intermittently giving errors saying requests cannot be sent ~~and I suspect its because my API request is being dropped~~ which I found was due to a VPN connection issue.
Describe the solution you'd like I would like to see the API key as a configurable option.
Describe alternatives you've considered I've considered trying to find the settings, or where the API is stored, but don't know where to look.
Additional context
I see that both this fork and the original extension are both hardcoded to use the same API key.
Allowing the end-user to obtain and use their own API key would help mitigate over-utilization of the hard-coded key.
Ok, so a little egg on my face regarding connection errors; I forgot that I was connected to a VPN that was full-tunneling my traffic, which was ultimately the root cause of my connection issue. However, I still think a configurable API key option would be beneficial.
As of tonight, we get an error: access denied in the widget. I wish we could change the API key easily.
Hello,
The same thing happens to me, when I connect to the company VPN I go out through a proxy. It seems that the plasmoid is not configured to get all the traffic through the http_proxy variable.
It would be to configure this part and it would be fixed.
Regards
