Page MenuHomePhabricator

Fix a CalendarExport issue when an existing export has an unsupported mode
ClosedPublic

Authored by epriestley on Feb 16 2017, 2:20 PM.
Tags
None
Referenced Files
F13970151: D17369.diff
Oct 17 2024, 5:59 AM
Unknown Object (File)
Oct 9 2024, 7:19 AM
Unknown Object (File)
Oct 1 2024, 9:45 PM
Unknown Object (File)
Sep 2 2024, 5:17 AM
Unknown Object (File)
Aug 27 2024, 3:03 AM
Unknown Object (File)
Aug 26 2024, 4:51 AM
Unknown Object (File)
Aug 25 2024, 10:33 AM
Unknown Object (File)
Aug 17 2024, 9:47 PM
Subscribers
None

Details

Summary

See D16676. When an export has an unsupported mode (bad database value, out-of-date object, etc) the intent of this code is to put it into the <select /> so that you can save the form without silently changing the object.

However, it incorrectly calls array_shift() instead of array_unshift().

Test Plan

Edited a Calendar export with an invalid mode, saw the mode appear properly in the dropdown:

Screen Shot 2017-02-16 at 6.18.11 AM.png (382×440 px, 28 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable