[TS migration] Migrate str to Typescript (expensify-common)#713
Conversation
Skalakid
left a comment
There was a problem hiding this comment.
LGTM, left some small comments connected to function descriptions, to make them have a consistent format
Co-authored-by: Michał Skałka <39538890+Skalakid@users.noreply.github.com>
Co-authored-by: Michał Skałka <39538890+Skalakid@users.noreply.github.com>
Co-authored-by: Michał Skałka <39538890+Skalakid@users.noreply.github.com>
Co-authored-by: Michał Skałka <39538890+Skalakid@users.noreply.github.com>
Co-authored-by: Michał Skałka <39538890+Skalakid@users.noreply.github.com>
Co-authored-by: Michał Skałka <39538890+Skalakid@users.noreply.github.com>
Co-authored-by: Michał Skałka <39538890+Skalakid@users.noreply.github.com>
Co-authored-by: Michał Skałka <39538890+Skalakid@users.noreply.github.com>
Co-authored-by: Michał Skałka <39538890+Skalakid@users.noreply.github.com>
Co-authored-by: Viktoryia Kliushun <vikstash@gmail.com>
|
🚀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
Strmodule to Typescript, it also removes almost all underscore usage from str and instead uses native JS.Fixed Issues
$ GH_LINK