gravitystorm created an issue (openstreetmap/openstreetmap-website#6550)
As part of our [i18n-js
configuration](https://github.com/openstreetmap/openstreetmap-website/blob/74a41d95fa146523bd856cd63452e1ed3c462696/config/i18n.yml),
we currently create a top-level `i18n` directory. It's used to hold [a single
template file under source
control](https://github.com/openstreetmap/openstreetmap-website/tree/74a41d95fa146523bd856cd63452e1ed3c462696/i18n/templates),
and a number of intermediate `.json` files created while generating the
corresonding `.js` files in `app/assets/javascripts/i18n/`
>From a developer experience point of view, it would be great to move these
>elsewhere, because:
* we've already got a lot of top-level directories, that e.g. push our readme
far down the page
* these files aren't important enough to warrant a top-level directory of their
own
* more importantly, it can mislead developers to think that this is where to
look for translation-related matters, when the vast majority of the time they
should look elsewhere e.g. `config/locales/`.
As far as I can tell we get free choice over the directory used, but I haven't
tested to see if i18n-js has any built-in reasons to prefer that specific
directory.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/6550
You are receiving this because you are subscribed to this thread.
Message ID: <openstreetmap/openstreetmap-website/issues/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
