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
See #18
When one of the tools is invoked with a path containing a ~, we should call -stringByExpandingTildeInPath: to expand it.
~
-stringByExpandingTildeInPath:
The text was updated successfully, but these errors were encountered:
Seems it's not an issue anymore (was it ever?) as I just tested with v0.5.0: swiftgen strings ~/Localizable.strings and it worked.
swiftgen strings ~/Localizable.strings
Maybe @AJ9 issue in #18 was finally not that ~ after all (but probably UTF8 encoding instead)
@AJ9 could you confirm?
Sorry, something went wrong.
Tested locally, I confirm this was not the issue and ~ works well. Plus, #21 is fixed now.
No branches or pull requests
See #18
When one of the tools is invoked with a path containing a
~
, we should call-stringByExpandingTildeInPath:
to expand it.The text was updated successfully, but these errors were encountered: