fixed a bug in MID function - substring was incorrectly used #45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jalateras
added a commit
that referenced
this pull request
Mar 19, 2016
fixed a bug in MID function - substring was incorrectly used
|
Hey Jim, |
|
I have published 1.0.7 |
|
The npm website still reports 1.0.6 as the latest version. npm install also gets 1.0.6 |
|
Check again, it should be there. |
|
Thanks Jim! I can see it now. On Sun, Mar 20, 2016 at 10:45 AM, Jim Alateras [email protected]
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The signature of substring is text.substring(begin, end), as opposed to MID(text, start, numberOfCharsToReturn).