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
..
CalendarTSRange.js	honor removing a time constraint	2019-02-19 13:42:26 -08:00
Camera.js	Merge branch 'new-schema'	2018-04-27 06:42:39 -07:00
JsonWrapper.js	Major refactoring of UI code, small UI changes. (#48)	2018-03-20 07:03:12 -07:00
Range90k.js	A little more UI refactor, cleanup, eslint more strict (#54)	2018-03-25 22:18:56 -07:00
Range.js	fix trailing whitespace in Javascript	2018-08-31 07:31:22 -07:00
Recording.js	Merge branch 'new-schema'	2018-04-27 06:42:39 -07:00
Stream.js	Merge branch 'new-schema'	2018-04-27 06:42:39 -07:00