mikesprague/localweather

:sun_behind_small_cloud: Minimalist local weather app powered by Visual Crossing

localweather's Issues

TypeError in /

Error in localweather-io

TypeError in /
undefined is not a function

View on Bugsnag

Stacktrace

js/vendors~main.bundle.js:24935 - registerValidSW
js/vendors~main.bundle.js:24926 - 
js/vendors~main.bundle.js:18608 - wrapped

View full stacktrace

Created automatically via Bugsnag

TypeError in /

Error in localweather-io

TypeError in /
undefined is not a function

View on Bugsnag

Stacktrace

js/vendors~main.bundle.js:23182 - registerValidSW
js/vendors~main.bundle.js:23173 - 
js/vendors~main.bundle.js:19382 - wrapped

View full stacktrace

Created automatically via Bugsnag

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

• CircleCI
• Travis CI
• Buildkite
• CodeShip
• Azure Pipelines
• TeamCity
• Buddy
• AppVeyor
  But Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

TypeError in /

Error in localweather-io

TypeError in /
undefined is not a function

View on Bugsnag

Stacktrace

js/vendors~main.bundle.js:26128 - registerValidSW
js/vendors~main.bundle.js:26119 - 
js/vendors~main.bundle.js:17888 - wrapped

View full stacktrace

Created automatically via Bugsnag

Error when getting next X hours if current hour of day less than 12 from end of day

There's currently an error if the current hour of the day is less than 12 hours from the end of the day.

This has to do with a difference in how the data is supplied from Visual Crossing vs how it used to be supplied by Dark Sky. Specifically, the current day hourly used to be supplied starting with the current hour and for the next 24 hours.

This wasn't discovered when refactoring for Visual Crossing due to the time of day I worked on it and prob a little bit of laziness.

Expected solution will be to always grab current and next days hours, merge them, and only use the data I need.

TypeError in /

Error in localweather-io

TypeError in /
undefined is not a function

View on Bugsnag

Stacktrace

js/vendors~main.bundle.js:24206 - registerValidSW
js/vendors~main.bundle.js:24197 - 
js/vendors~main.bundle.js:17904 - wrapped

View full stacktrace

Created automatically via Bugsnag

TypeError in /

Error in localweather-io

TypeError in /
undefined is not a function

View on Bugsnag

Stacktrace

js/vendors~main.bundle.js:24996 - registerValidSW
js/vendors~main.bundle.js:24987 - 
js/vendors~main.bundle.js:18667 - wrapped

View full stacktrace

Created automatically via Bugsnag

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

• CircleCI
• Travis CI
• Buildkite
• CodeShip
• Azure Pipelines
• TeamCity
• Buddy
• AppVeyor
  But Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Additional weather sources

Hi,

I was just browsing Github and stumbled across your project. I created a free weather API. Would you be interested to integrate an additional weather provider? Let me know if you need additional weather variables or features.

Best, Jeff