-
Notifications
You must be signed in to change notification settings - Fork 15
Check if startsWith exists before setting it #14
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
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
@karthiknadig Thank you very much for the improvement! However, there's some CI failed. I know it's not related to this PR, but in order to make all the CI green to this PR, could you please fix them as well? Appreciate it. |
@huan Looks like |
Thank your very much, merged! |
@huan Any idea when this will be published? |
I have not checked if our CI can publish the latest code automatically. If it's not, then the publish will depend on how the release strategy is defined by @simonepri |
Hi there, sorry for being late and thanks for contributing! About the CI, I think it was discussed already but the idea is that we need to do a new major release before removing node 4 etc to fix the ci. So in order for me to release this asap my idea would be to revert all changes but the fix itself. |
@simonepri Works for me. |
This reverts commit 5ebe846.
Closes #14 #15 Co-Authored-By: Karthik Nadig <[email protected]>
Closes #14 #15 Co-Authored-By: Karthik Nadig <[email protected]>
Closes #13