-
Notifications
You must be signed in to change notification settings - Fork 2
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
Added base64, image.png, wasm data: to image, (limited) support for namespaces (virtual map access). moved the image functions under image.* #217
Conversation
…mage function under image.*
…for image producing
for _, b := range []byte(name) { | ||
if !lexer.IsAlphaNum(b) { | ||
return false | ||
} | ||
} |
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.
Usually it's better to loop on runes from a string
Unicode characters such as accent, and emoji are badly checked otherwise
Then Unicode package can be used to check the type
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.
it's on purpose (for now at least) only bytes (ascii) is allowed outside of strings
unicode does work fine inside strings (as demoed in many examples)
@@ -380,6 +380,7 @@ func EvalOne(ctx context.Context, s *eval.State, what string, out io.Writer, opt | |||
}() | |||
} | |||
s.SetContext(ctx, options.MaxDuration) | |||
defer s.Cancel() |
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.
This is the fix for the wasm errors! (#204 )
Fixes #212
Fixes #204