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
F18184923: D15725.id37895.diff
Sat, Aug 16, 2:36 PM
F18110108: D15725.diff
Mon, Aug 11, 4:19 PM
F18110014: D15725.id37893.diff
Mon, Aug 11, 3:35 PM
F18106403: D15725.id37894.diff
Sun, Aug 10, 10:33 PM
F18106343: D15725.id.diff
Sun, Aug 10, 10:16 PM
F18101970: D15725.diff
Sat, Aug 9, 5:10 PM
F18085957: D15725.id.diff
Tue, Aug 5, 7:29 PM
F17924343: D15725.id37892.diff
Wed, Jul 30, 9:51 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.