skolmer / i18n-tag-schema Goto Github PK

i18n-tag-schema ./src generates a required value for every occurrence, not only once.
i.e. using { i18nStart } three times in the project generates "required": ["Start","Start","Start"] and this throws an npm error Error: schema is invalid: data.required should NOT have duplicate items

The devDependency semantic-release was updated from 15.13.11 to 15.13.12.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

i18n-tag-schema ./translations --validate --schema ./translation.schema.json throws an npm error if translation is invalid

npm/npm#2097

A working preprocessor is already implemented in the next branch.

TODO:

• Extract v2.0 typescript preprocessor into a separate node module.
• Add configuration/api to implement custom preprocessors.

The test coverage is pretty low at the moment. This needs to be improved.

I was running into an issue using TypeScript 3.7 with optional chaining and React Fragments using empty tags (<>...</>). In order to get both working properly the TypeScript preprocessor needs some minimal changes:

diff --git a/node_modules/i18n-tag-schema/dist/lib/preprocessors/typescript.js b/node_modules/i18n-tag-schema/dist/lib/preprocessors/typescript.js
index 0e5cd94..60923e3 100644
--- a/node_modules/i18n-tag-schema/dist/lib/preprocessors/typescript.js
+++ b/node_modules/i18n-tag-schema/dist/lib/preprocessors/typescript.js
@@ -15,8 +15,8 @@ exports.default = function (contents, filePath) {
   if (!ts) throw new Error('cannot find typescript compiler. check if \'typescript\' node module is installed.');
   var processed = ts.transpileModule(contents, {
     compilerOptions: {
-      target: ts.ScriptTarget.Latest,
-      jsx: path.extname(filePath) !== '.ts' ? ts.JsxEmit.Preserve : ts.JsxEmit.None
+      target: ts.ScriptTarget.ES2020,
+      jsx: path.extname(filePath) !== '.ts' ? ts.JsxEmit.React : ts.JsxEmit.None
     }
   });
   if (processed && processed.outputText) {

By setting ES2020 we force transpiling optional chaining syntax (such as foo?.bar and foo ?? bar). ts.JsxEmit.React is needed for proper fragment support.

Custom translations groups should be added to the schema.

i18n('my custom group')`my fancy string`

shoud be validated as:

"my custom group": {
  "my fancy string": "some translation"
}

and

@i18nGroup('my custom group')
class App {
  getFancyString() {
    return this.i18n`my fancy string`
  }
  getCommonString() {
    return i18n('common')`my fancy string`
  }
}

shoud be validated as:

"my custom group": {
  "my fancy string": "some translation"
},
"common": {
  "my fancy string": "some other translation"
}

The devDependency travis-deploy-once was updated from 5.0.7 to 5.0.8.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

travis-deploy-once is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hi, fantastic work! would you consider supporting typescript? Currently it requires only JS files. Thanks!

by @tomitrescak
skolmer/vscode-i18n-tag-schema#2

Replace crlf with lf line endings for crossplatform translation support

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

TODO

• fix --filter flag ✅
• display progress indicator ✅
• add preprocessor argument #16 ✅

When calling transpileModule on a plain .ts file, with certain generic expressions and when jsx is set to ts.JsxEmit.Preserve, incorrect JS will be emitted. For example:

const ts = require('typescript');

const contents = `
const something = <T>(a: T) => {
}
`;

const processed = ts.transpileModule(contents, {
    compilerOptions: {
        target: ts.ScriptTarget.Latest,
        jsx: ts.JsxEmit.Preserve
    }
});

console.log(processed.outputText);

will emit:

const something = <T>(a: T) =>
</>;

Which will cause errors when Babylon tries to parse it.

Version 5.1.6 of ajv just got published.

This version is covered by your current version range and after updating it in your project the build failed.

ajv is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

exported vaidateSchema function fails if the schema contains multiline template literal

related: ajv-validator/ajv#226