You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
When using the extract cli command and the minimal format, I expect the output to be a correctly formatted JSON representation of the catalog.
I find that the file is not formatted correctly as the last line of the file fails to include a \n character as every line should according to POSIX standard.
To Reproduce
Extract some translations using the cli and specify the minimal format, notice there is no newline character at the end of the final line at the end of the file.
Expected behavior
A clear and concise description of what you expected to happen.
When using the extract cli command and the minimal format, I expect the output to be a correctly formatted JSON representation of the catalog.
I find that the file is not formatted correctly as the last line of the file fails to include a \n character as every line should according to posix standard.
Additional context
Add any other context about the problem here.
It may be useful to some people to retain the existing incorrect absence of a \n in some cases
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug
A clear and concise description of what the bug is.
When using the
extract
cli command and the minimal format, I expect the output to be a correctly formatted JSON representation of the catalog.I find that the file is not formatted correctly as the last line of the file fails to include a
\n
character as every line should according to POSIX standard.To Reproduce
Extract some translations using the cli and specify the minimal format, notice there is no newline character at the end of the final line at the end of the file.
Expected behavior
A clear and concise description of what you expected to happen.
When using the extract cli command and the minimal format, I expect the output to be a correctly formatted JSON representation of the catalog.
I find that the file is not formatted correctly as the last line of the file fails to include a
\n
character as every line should according to posix standard.Additional context
Add any other context about the problem here.
It may be useful to some people to retain the existing incorrect absence of a
\n
in some casesPrior Art: https://github.com/sindresorhus/write-json-file/blob/main/index.js#L37-L44
lingui --version
npm list @babel/core
.babelrc
) or framework you use (Create React App, Meteor, etc.)The text was updated successfully, but these errors were encountered: