-
Notifications
You must be signed in to change notification settings - Fork 150
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
i18n breaks usage outside of jsonschema2md repo #157
Comments
@trieloff I was building the path myself and not over the path.resolve/join like in other code part. I will make a branch with the fix. Is there a way how I could run that test on a branch? |
the i18n path was build by strings. now it use path to resolve it fix adobe#157
Just reading the error message
it looks like the problem is that The bigger question is: why do we have to create the directory anyway? |
there was an bug in the init part of the i18n setup. It was moved to the cli to handle it in the same way fix adobe#157
I found the error. I have setuped the i18n lib in the file readmeWriter.js in the wrong way. Then I saw if i would setup it into the cli.js i just would need to do it once and not twice. So i have moved the init part of the i18n to the cli.js. Now to your question. The i18n lib will create a file in the provided directory if the file did not exists. |
When run without arguments, then it should just take the i18n file from the project's |
Thank you, @Claymore1337 – much appreciated! |
🎉 This issue has been resolved in version 3.1.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
## [3.1.1](adobe/jsonschema2md@v3.1.0...v3.1.1) (2019-07-31) ### Bug Fixes * **i18n init:** moved the i18n init part to the cli.js ([5e37d2d](adobe@5e37d2d)), closes [adobe#157](adobe#157) * **markdownwriter.js:** use path function to resolve the path ([5fe7db2](adobe@5fe7db2)), closes [adobe#157](adobe#157)
Hi @Claymore1337 it looks like the latest release is broken when used from
node_modules
of another project:See also adobe/helix-pipeline#432
The text was updated successfully, but these errors were encountered: