Page MenuHomePhabricator

Time controls should format end date value correctly (not 5:0 PM)
ClosedPublic

Authored by lpriestley on Apr 15 2016, 7:11 PM.
Tags
None
Referenced Files
F13285189: D15725.diff
Mon, Jun 3, 4:25 PM
F13278056: D15725.id37894.diff
Fri, May 31, 6:20 PM
F13277800: D15725.id37895.diff
Fri, May 31, 1:42 PM
F13277799: D15725.diff
Fri, May 31, 1:41 PM
F13254983: D15725.id37892.diff
Sat, May 25, 4:17 AM
F13240232: D15725.id37894.diff
Wed, May 22, 12:01 PM
F13229477: D15725.diff
Mon, May 20, 4:43 PM
F13227285: D15725.id.diff
Mon, May 20, 2:22 AM
Subscribers

Details

Summary

Fixes T9296

Test Plan

Create an event, change start time to 3PM, end value should update to 4:00 PM, not 4:0 PM

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

lpriestley retitled this revision from to Time controls should format end date value correctly (not 5:0 PM).
lpriestley updated this object.
lpriestley edited the test plan for this revision. (Show Details)
lpriestley added reviewers: epriestley, chad.
lpriestley edited edge metadata.

oops, wrong direction

epriestley edited edge metadata.

Run bin/celerity map to clear that test issue.

webroot/rsrc/js/core/behavior-time-typeahead.js
139–142

You shouldn't need the end_minutes === 0 part I think since 0 < 9?

This revision is now accepted and ready to land.Apr 15 2016, 7:15 PM
webroot/rsrc/js/core/behavior-time-typeahead.js
139–142

Haha yeah I got a little too excited about finding the problem

lpriestley edited edge metadata.

celery sticks

This revision was automatically updated to reflect the committed changes.