Skip to content
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

Update from upstream repo ady624/webCoRE@master #11

Open
wants to merge 333 commits into
base: master
Choose a base branch
from

Conversation

backstroke-bot
Copy link

Hello!

The upstream repository ady624/webCoRE@master has some new changes that aren't in this fork. So, here they are, ready to be merged! 🎉

If this pull request can be merged without conflict, you can publish your software with these new changes. Otherwise, fix any merge conflicts by clicking the Resolve Conflicts button.


If you like Backstroke, consider donating to help us pay for infrastructure here. Backstroke is a completely open source project that's free to use, but we survive on sponsorships and donations. Thanks for your support! Help out Backstroke.


Created by Backstroke (I'm a bot!)

idpaterson and others added 30 commits August 26, 2018 19:37
…pdowns when the Chrome browser's autofill-type-predictions feature is enabled
…"(unknown)" SHM status, fixed string to date across DST thanks @bangali, null routines, integer trailing zero cast, saving large pistons and disappearing variables on mobile
…cker dropdowns when the Chrome browser's autofill-type-predictions feature is enabled

This is a bit too destructive, will need more testing in the next release.
…"(unknown)" SHM status, fixed string to date across DST thanks @bangali, null routines, integer trailing zero cast, saving large pistons and disappearing variables on mobile
…and CUSTOM request body for local network requests
… like ST has a lot of trouble reading the list of devices/commands/attributes/values these days, so giving up on reading values makes this much faster - temporarily?!
* master:
  v0.3.109.20181207 - BETA M3 - Dirty fix for dashboard timeouts: seems like ST has a lot of trouble reading the list of devices/commands/attributes/values these days, so giving up on reading values makes this much faster - temporarily?!
… location's preferred temperature scale if different units than the provided value
For example, < is encoded as &lt; but the lt() function matches and highlights that, which breaks the HTML entity.
Fixes avg( breaking the expression due to an unterminated group
Do not highlight [ and : in the device expression because it's hard to highlight the closing ], same for the ( in function calls
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants