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
F19015814: D15725.id37894.diff
Sun, Nov 23, 1:53 AM
F19013488: D15725.diff
Sat, Nov 22, 3:30 PM
F18986794: D15725.id37895.diff
Mon, Nov 17, 5:05 PM
F18835347: D15725.id.diff
Sun, Oct 26, 3:15 PM
F18807869: D15725.diff
Oct 19 2025, 3:33 AM
F18805882: D15725.id37892.diff
Oct 18 2025, 4:54 PM
F18763805: D15725.id.diff
Oct 7 2025, 2:19 AM
F18736352: D15725.id37895.diff
Oct 1 2025, 5:32 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.