We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We're doing npx ttag update ./i18n/en-CA.po ./src command. In OSX that generates forward slashes:
npx ttag update ./i18n/en-CA.po ./src
#: src/constants.js:10
In windows that generates back slashes:
#: src\constants.js:10
That creates useless noise in git diff. Can that be prob normalized?
The text was updated successfully, but these errors were encountered:
Hi @dy! Is it ok if we will leave only the first way of formatting?
Sorry, something went wrong.
@AlexMost absolutely, I prefer / - that's the standard path style and windows understands that too.
/
Any hints on how to do that? This still happens here.
No branches or pull requests
We're doing
npx ttag update ./i18n/en-CA.po ./src
command.In OSX that generates forward slashes:
#: src/constants.js:10
In windows that generates back slashes:
#: src\constants.js:10
That creates useless noise in git diff.
Can that be prob normalized?
The text was updated successfully, but these errors were encountered: