-
Notifications
You must be signed in to change notification settings - Fork 136
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
[TS migration] Migrate str to Typescript (expensify-common) #713
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, left some small comments connected to function descriptions, to make them have a consistent format
Co-authored-by: Michał Skałka <[email protected]>
Co-authored-by: Michał Skałka <[email protected]>
Co-authored-by: Michał Skałka <[email protected]>
Co-authored-by: Michał Skałka <[email protected]>
Co-authored-by: Michał Skałka <[email protected]>
Co-authored-by: Michał Skałka <[email protected]>
Co-authored-by: Michał Skałka <[email protected]>
Co-authored-by: Michał Skałka <[email protected]>
Co-authored-by: Michał Skałka <[email protected]>
Co-authored-by: Viktoryia Kliushun <[email protected]>
🚀Published to npm in v2.0.10 |
Hmmm, now that
I wonder if the Web-Expensify project supports |
@aldo-expensify What command do you use to update |
hmm I updated manually the |
Yes, this is because with TS there is a build step before the package is published to NPM. It was introduced here. You can also try building locally to test your changes ( |
The PR aims to migrate
Str
module to Typescript, it also removes almost all underscore usage from str and instead uses native JS.Fixed Issues
$ GH_LINK