6f0c8c19de
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. |
||
|---|---|---|
| .. | ||
| models | ||
| support | ||
| views | ||
| MoonfireAPI.js | ||