Skip to content
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

updated docs needed for 2.0.0 #1790

Closed
MaxMillington opened this issue Nov 30, 2023 · 1 comment · Fixed by osmosis-labs/osmosis-frontend#2490
Closed

updated docs needed for 2.0.0 #1790

MaxMillington opened this issue Nov 30, 2023 · 1 comment · Fixed by osmosis-labs/osmosis-frontend#2490
Assignees
Labels
type: documentation Improvements or additions to documentation type: improvement Something that can be improved.

Comments

@MaxMillington
Copy link

Problem

I upgraded my inlang to 2.0.0. Now, my scripts no longer work:

"machine-translate": "inlang machine translate && yarn fix-machine-translate",
 "fix-machine-translate": "node fix-machine-translate.js"
yarn machine-translate
yarn run v1.22.19
$ inlang machine translate && yarn fix-machine-translate
error: required option '--project <path>' not specified
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

It looks like in the new version of inlang, the project option is now required and it is expecting a format of {name}.inlang , but in the docs, it still says that the root is the default and that inlang will look for a project.inlang.json file.

Proposal

Can we get updated docs in the read.me and ideally a quick migration guide?

@maige-app maige-app bot added type: documentation Improvements or additions to documentation type: improvement Something that can be improved. labels Nov 30, 2023
@samuelstroschein samuelstroschein self-assigned this Nov 30, 2023
@samuelstroschein
Copy link
Member

@MaxMillington I opened osmosis-labs/osmosis-frontend#2490 to fix the issue on your side.

The auto migration for #1678, in combination with updating to v2 of the CLI simultaneously, did not work. I updated the docs and removed the reference of the root file.

PS with the project directory you can soon move the project into your frontend folder. There won't be a need for projects at the root of a repo anymore :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: documentation Improvements or additions to documentation type: improvement Something that can be improved.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants