Importing menus items are always disabled

1. We can remove the stupid "? TRUE : FALSE".
2. We should check previous versions where "1" was used and try both solutions: in_array($menuLink['expanded'], ['1', TRUE], TRUE)

Updating patch as suggested in comment #3
Since the patch in comment #2 is not getting applied, so could not create Inter-diff file.

Tested path #4 and it is working. Administration menu items are enabled on import.

The patch at #4 also solved the issue for me.

In my case, I exported menus locally as I usually would, but when I deployed and imported using drush im (full), the menus items exist, but they are always disabled. With the patch, it now works as expected (menu items exists and are enabled if they were set so).

Setting the priority to "Critical" as the drush im is basically broken without this patch.

For those interested in correctly exporting menus locally and then importing on production, here are the steps:

1. On local, add/delete your menus.
2. drush em
3. drush cex
4. git commit all changed files
5. On production: drush cim, then drush im

In typical deployments, drush updb is usually run first, so you can write a hook_update like this:

/**
 * Run drush im.
 */
use Drush\Drush;
function YOURCUSTOMMODULE_update_9007(&$sandbox) {
  /** @var \Consolidation\SiteAlias\SiteAliasManager $alias_manager */
  $alias_manager = Drush::service('site.alias.manager');
  $selfRecord = $alias_manager->getSelf();
  $options = ['choice' => 'full'];
  Drush::processManager()->drush($selfRecord, 'cim', [])->mustRun();
  Drush::processManager()->drush($selfRecord, 'im', [], $options)->mustRun();
}

This will import your config first, then import your menus. So then you do not need to manually run drush im on production.

Basically you need to run drush cim first because it will import the structure_sync config. Only then you can run drush im.

(Change 9007 to match your hook_update numbering)

Thanks for the reviews !