Use JSON_PRETTY_PRINT to encode JSON so config files are more readable and diffs work

Attached patch formats the JSON in the config using JSON_PRETTY_PRINT.

Note that, before the patch, the TB Mega Menu code called Json::encode($menuConfig) which made this call:

public static function encode($variable) {
  // Encode <, >, ', &, and ".
  return json_encode($variable, JSON_HEX_TAG | JSON_HEX_APOS | JSON_HEX_AMP | JSON_HEX_QUOT);
}

The patched code now just calls json_encode() directly with those same options plus JSON_PRETTY_PRINT.

Related:

There is a core issue suggesting that optional parameters should be added to Json::encode($menuConfig) to allow passing of flags:

📌 Json::encode() and Json::decode() limit what we can do with JSON Needs work

If that patch does land, this code could be updated. Until then, this patch uses the suggested workaround of just calling json_encode() directly so we can pass our own flags.

@jrb,

I love this. Thank you.

I just tested your patch. Everything works as expected on config import and export. The JSON config is now readable.
I'll commit this to the 2.x branch and include it in a future release. Thanks again.

For Drupal 9: Use https://www.drupal.org/project/tb_megamenu/releases/2.0.0-alpha6 →
For Drupal 10: use https://www.drupal.org/project/tb_megamenu/releases/3.0.0-alpha1 →

Automatically closed - issue fixed for 2 weeks with no activity.