-
Notifications
You must be signed in to change notification settings - Fork 390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC-002 - Catalogs #326
RFC-002 - Catalogs #326
Conversation
6b0b374
to
a6d3d52
Compare
Codecov Report
@@ Coverage Diff @@
## next #326 +/- ##
=======================================
Coverage ? 84.11%
=======================================
Files ? 37
Lines ? 1190
Branches ? 294
=======================================
Hits ? 1001
Misses ? 118
Partials ? 71
Continue to review full report at Codecov.
|
a6d3d52
to
c8d84c2
Compare
and? |
Any news on this ? |
Hey @abhashmi, @ahmed-belal, @alexarnautu, @Photonios and @cipix2000! 👋 I saw your great work in lingui-multi. New configuration for catalogs seems to solve exactly the same problem. I wonder if you could give me your feedback on this RFC? I'm planning to merge it into pre-release this week. The PR is almost ready, I'm just thinking about the final format of configuration: mapping {[path: string]: CatalogConfig} {
"lingui": {
"catalogs": {
"./locale/{locale}/shared": [
".",
"!./node_modules/"
],
"./locale/{locale}/graphql": "run!scripts/fetch_graphql_enums.js",
"./components/{name}/locale/{locale}": "./components/{name}/",
}
}
} list of catalog configs
I think I tried both, because most of codebase uses the first format, while one part uses the second format. It's probably unimportant, but the first one seems to be more readable, while the second one is more explicit. What do you think? |
If it's used, it complains about invalid syntax in TS types and interfaces without dangling commas.
Implementation of RFC-002
Resolves #257
Work in progress:
catalogs
locales
to configuration@lingui/conf
referenceIn next batch: