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
https://forum.snap.berkeley.edu/t/substring-after/18538
The text was updated successfully, but these errors were encountered:
yep, that's a bug, I think it can be fixed by simply filling in the missing zero in the very last input slot of this definition body script:
That's what I'm planning to do. Any objections?
Sorry, something went wrong.
The problem is that in previous versions (I tried 9.2.17), an input type declared as number would return 0 if called with an empty value
Whereas now it returns the empty value
There could be more of these lurking around
Oh, is this a side effect of the change to number parsing introduced for the sake of RANDOM?
Yes, it is. Now I think I'm going to fix it in Snap! and leave the library as it is, so existing projects won't break...
jmoenig
No branches or pull requests
https://forum.snap.berkeley.edu/t/substring-after/18538
The text was updated successfully, but these errors were encountered: