You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had an interesting use case, where I needed to merge 8-9 locale files in a rails app into a single app.
Easily done, I thought, and quickly concatenated all the files, and then ran yalphabetize -a over the final file.
And sadly noted that each of the files stayed in it's own en: block... ah well, I deleted all of the YAML heading lines, and ran it again, but still ended up with:
Is there a flag / option (or previous attempt?) of allowing "key merging" during the yalphabetize run?
I guess you ideally don't want the operation to ever be "lossy", meaning you'd not want two identically named YAML nodes with actual values (string or array) to clobber each other, and I'll admit I'm firing this idea out without really having a solid grasp on the underlying YAML data model to know if these two scenarios are easily identified when parsing files.
What are the thoughts around this? Possible? Or fraught with peril? Worth even looking into?
The text was updated successfully, but these errors were encountered:
I had an interesting use case, where I needed to merge 8-9 locale files in a rails app into a single app.
Easily done, I thought, and quickly concatenated all the files, and then ran
yalphabetize -a
over the final file.And sadly noted that each of the files stayed in it's own
en:
block... ah well, I deleted all of the YAML heading lines, and ran it again, but still ended up with:Rather than the desired outcome of:
Is there a flag / option (or previous attempt?) of allowing "key merging" during the yalphabetize run?
I guess you ideally don't want the operation to ever be "lossy", meaning you'd not want two identically named YAML nodes with actual values (string or array) to clobber each other, and I'll admit I'm firing this idea out without really having a solid grasp on the underlying YAML data model to know if these two scenarios are easily identified when parsing files.
What are the thoughts around this? Possible? Or fraught with peril? Worth even looking into?
The text was updated successfully, but these errors were encountered: