Traversing YAML data before import? about serge

[erikogan]

Caveat: This assertion is also based on my misunderstanding of the bug in parse_yaml raised in #17. It may be completely moot once that is fixed.

[iafan]

I think to address this in the most useful manner (for real-life situations like localizing Ruby-on-Rails apps and allowing to initially import translations from RoR localization files) we could introduce a new yaml_mode option similar to what we have in the XML parser. This setting would have two possible values: generic (default; would fall back to the current behavior) and rails.

In such rails mode:

1. the parser would ignore the root node name, assuming it's a language name, and exclude it from the built $path value. This would allow us to use path as a key callback value for serge import to work properly (an issue raised in #17);
2. when constructing the localized YAML file, the parser would replace the name of the root node with the target language name.

[erikogan]

Perfect. This is (similar to) what I thought originally, before saying, “I wonder if I can abstract it a bit to make it more generally useful.” But I was likely future-tripping. If a more general form of the yaml_mode needs to be added we can cross that bridge when we come to it.

So in the generic case the key argument passed to the callback would be the whole path, whereas in rails it would trim the locale from the head of the key. That makes sense. I haven’t looked at the code that constructs the localized YAML file, I’ll do that now.

[erikogan]

This issue has been resolved by PR #20.