willbooster / gen-i18n-ts Goto Github PK

Test case:
{
“123456”: “numeric key”
}

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Test Case: zh-tw.json

from #1 (comment)

temp directory does not exist. It's inconvenient...
We need to search how to manage a software for code generation.

Not functions in a function, but private methods in a class

https://github.com/tc39/proposal-set-methods

if a key is in the default language file but not in a non-default language file

• key-value pair in default should be added to the non-default
• some warning message should be shown

if a key is in a non-default language file but not in the default language file

• the key will be ignored in the output object
• some warning message should be shown

ja.json

{
  test: ${a} and ${b}
}

output object

{
   test: function (a: string, b: string) => string
}

test("${b}", "foo") will be "foo and foo" though "${b} and foo" is expected

WillBooster内のプロジェクトでは原則noUncheckedIndexedAccessをtrueに設定しているが、本ツールが生成したコードはそれを満たしていないので型エラーが発生させる。

hard to know what each test is for

i18n-1 -> basic
i18n-2 -> multiArgs
...
i18n-8 -> yaml

🚨 The automated release from the release branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the release branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

c.f. 59fbfb4#diff-87db21a973eed4fef5f32b267aa60fcee5cbdf03c67fafdc2a9b553bb0b15f34L30

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Datasource	Name	Replacement PR?
npm	@babel/plugin-proposal-class-properties
npm	@babel/plugin-proposal-numeric-separator

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): update all non-major dependencies (@types/node, @typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• chore(deps): lock file maintenance

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency build-ts to v13
• chore(deps): update dependency eslint to v9
• chore(deps): update dependency semantic-release to v24
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

params of functions in output object should be merged.
ja.json (default)

{
  hello: "こんにちは、${name}さん！"
}

en.json

{
  hello: "Hello, ${userName}!"
}

fr.json

{
  hello: "Bonjour!"
}

output:

 hello: (name: string, userName: string) => string

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.