Scott Lamb 6f0c8c19de honor removing a time constraint ... Looks like a bug got introduced with the great UI rewrite: when you add a (start or end) time constraint, then remove one, the change wouldn't be reflected. Within CalendarTSRange, it used null to mean to keep a value, and || to check if it was null. These meant empty strings turned into the existing value, instead of no constraint as they should be. This was unnecessarily clever; stop doing that. Also keep the console logging in the deployed config; it's harmless and eases debugging.		2019-02-19 13:42:26 -08:00
..
parts	A little more UI refactor, cleanup, eslint more strict (#54)	2018-03-25 22:18:56 -07:00
base.config.js	couple fixes to the dialog close button	2018-04-28 06:39:29 -07:00
dev.config.js	A little more UI refactor, cleanup, eslint more strict (#54)	2018-03-25 22:18:56 -07:00
NVRSettings.js	Major refactoring of UI code, small UI changes. (#48)	2018-03-20 07:03:12 -07:00
prod.config.js	honor removing a time constraint	2019-02-19 13:42:26 -08:00