List view

• Avoid Translating Placeholders

  4-step plan to avoid translating placeholders using, Google Translate, AWS, e.t.c 1. When extracting from a source file, `.pot, .xlf, ...,` the placeholders should be in MessageFormat2. `{$var} ...`, due to formatting differences between different files and languages, there should also be additional information about how the placeholder is formatted. `{$var :Placeholder format=printf-style} ...` 2. Adjust `MessageFormat2` parser, to reflect new changes 3. When sending to 3rd party translate services: extract all `node.Text`, translate them, replace original `node.Text` with translated ones. 4. When converting back to file, `.pot, .xlif,...,` convert MessageFormat2 string to normal string, using information about placeholder type. e.g. `{:Placeholder format=printf-style type=string}`, then placeholder should be converted to `%s`

  No due date

  •2/2 issues closed
  100% complete0 open2 closed

• Add Instrumentation for Tracing in Integration Tests

  1. Add instrumentation to integration tests 2. Show failed tests, in Jaeger with messages 3. Ignore automatic instrumentation errors, e.g when testing an invalid argument, the gRPC request is errored, when it should not be in Jaeger. (it seems that it is impossible) 4. Add tracing to CLI tests

  No due date

  •2/2 issues closed
  100% complete0 open2 closed