Sam A. Horvath-Hunt

Desirable?

Current output: ``` translations.json:3:29: | 3 | "message": "Some words {mySelect, select, other {}} {myCardinal, plural, =1 {} =1 {}}" | ^^^^^^^^ redundant-select: Select named `mySelect` is redundant as it...

Reuse lint/parser infra for invalid keys error printing

1

See #179.

Webpack & tsc plugins

3

The current Web workflow works pretty nicely with intlc able to compile everything in under a second, but it adds some extra moving parts separate from the main builds. What...

Syntax highlighting in editors

1

Tree-sitter? See also #185 (https://www.reddit.com/r/ProgrammingLanguages/comments/t4c8ms/what_parsing_techniques_do_you_use_to_support_a/hyxj3a8/).

This could be fun. Doable now with the parser keeping source information. Could inform you during editing of any linting issues, or any parsing failures.

As a starting point a formatter at `intlc format` which simply parses each ICU message in a dataset and compiles them back out, which would normalise spacing. It could then...

Prettified codegen

2

It's all on a single line at the moment. We'll probably run Prettier against it in web, but ideally the output would be more legible out of the box.

Wondering if this might be preferable for JS environments that don't support JSX syntax but still want React-ish (see #33) output. Instead of `{x.foo}`, a series of nested function calls?

Offset plurals

1

Example of the syntax: https://lingui.js.org/ref/message-format.html ``` {count, plural, offset:1 =0 {Nobody read this message} =1 {Only you read this message} one {You and # friend read this message} other {You...