Thank you for your feedback!
My only "complaint" is the folder name
"config". But that might just
be part of the example patch.
That was a correct assumption. I've now updated the name of the parameter to
`TranslationAliasesDirs` and renamed the name of that folder to `aliases`
Why can't we make the new structure
part of
the existing i18n/en.json file? Or if you really think the
separation is beneficial, why not have separate folders for
"specialpagealiases", "magicwords", and so on?
The main reason for separation was the concerns highlighted here:
https://phabricator.wikimedia.org/T89947#8210010
Another couple of reasons are related to change tracking being cleaner if these are in
their own files and it being easier for translatewiki
to process these files and perform stricter validation for them.
Or if you really think the
separation is
beneficial, why not have separate folders for
"specialpagealiases", "magicwords", and so on?
That would be possible with the current format:
```
"TranslationAliasesDirs": {
"TranslationNotificationsSpecialPageAlias": "i18n/aliases/",
"TranslationNotificationsSpecialMagicWords": "i18n/magicWords/",
"TranslationNotificationsSpecialNamespaceAlias":
"i18n/namespaceAlias/"
}
```
This makes it a lot more flexible for any
unpredictable future
addition. However, I would make it uppercase
"SpecialPageAliases" to
be closer to how extension.json works.
This should be doable. I'll check it out.