Export bundle 'config' field to features

I think it may be better to split this issue.
Exporting bundle 'config' key is critical but pretty printing the feature generated code is not and should be moved to a separate issue (with the corresponding patch).
The patch for the remaining concerns of this issue would become trivial and more prone to be quickly reviewed & committed.

I totally agree with you.

The patch works great here.
We now have 'language' related bundle settings included in features exports as well as our custom 'tsid' property bundle settings (see eck_i18n sandbox[1]).
IMHO this is a useful one-liner patch that should be committed.

Would be great is someone else who tested this fix could post its feedback in order to RTBC this issue.

[1] http://drupal.org/sandbox/garphy/1966680

Had a look at the single line patch that adds config to the export array and it is exactly what we need.

Works perfectly, although I might suggest that we have the contents in alphabetical order (as that is what features 2 exports it as).

It would be good if this could be merged.

Re-rolling the patch to allow it to be applied against the current Master.

Testet patch from #3 https://www.drupal.org/node/1867614#comment-7463046. Can confirm that this adds language settings to the feature.

I can confirm that patch #3 works with my RC4 installation of eck.

I had to force revert the features, but finally the bundle settings were updated on our development instance.

I guess if some config that eck supports is not going into a feature that is a bug, and not a feature..

+1 for the patch in #3.

Also note that it's currently impossible to revert bundles in Features, but this is fixed with the patch in #1733312-3: Bundles duplicates can be created from code - Features revert with bundles creates duplicates.