From 01f277cef22c5473296c9b4cf021eba816a748dc Mon Sep 17 00:00:00 2001
From: epriestley <git@epriestley.com>
Date: Thu, 16 Feb 2017 06:18:23 -0800
Subject: [PATCH] Fix a CalendarExport issue when an existing export has an
 unsupported mode

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:

{F2957321}

Reviewers: vrana, chad

Reviewed By: vrana

Differential Revision: https://secure.phabricator.com/D17369
---
 .../calendar/editor/PhabricatorCalendarExportEditEngine.php     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/applications/calendar/editor/PhabricatorCalendarExportEditEngine.php b/src/applications/calendar/editor/PhabricatorCalendarExportEditEngine.php
index 6ebbc9e1e0..8cd35e7323 100644
--- a/src/applications/calendar/editor/PhabricatorCalendarExportEditEngine.php
+++ b/src/applications/calendar/editor/PhabricatorCalendarExportEditEngine.php
@@ -70,7 +70,7 @@ final class PhabricatorCalendarExportEditEngine
 
     $current_mode = $object->getPolicyMode();
     if (empty($export_modes[$current_mode])) {
-      array_shift($export_modes, $current_mode);
+      array_unshift($export_modes, $current_mode);
     }
 
     $mode_options = array();