-
Notifications
You must be signed in to change notification settings - Fork 570
Bug in externalize, internalize functions #825
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
Comments
It might be nice if we have a Docker image to execute this? |
You mean as part of the CI pipeline? Or that someone can install and run locally? The latter sounds like more hassle to use than installing the direct requirements. |
I meant the latter. Is this so hassle? I don't have a strong opinion but in my opinion Docker feels safer than installing npm and their libs. This is just my preference :-) |
Well, it's a hassle for anyone who doesn't already have Docker installed. Docker also isn't especially natural for simple input/output operations, although I'm sure that can be worked around. |
Uh oh!
There was an error while loading. Please reload this page.
There's a bug in the externalize and internalize prelude functions. They both access the first struct field before checking if there's no fields (here and here)... here's a simple demo which throws a JS exception
Cannot read property 'prop' of undefined
:https://play.jsgo.io/308c189e795b573511cbc4d4606af6b0a60a065a
I've fixed it here: #824
p.s. I don't have node so I didn't run the uglify script... Perhaps someone can do that for me?
The text was updated successfully, but these errors were encountered: