You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IMO JavaScriptKit should only contain portable classes — ones that would work in most (if not all) JS environments. DOM-specific types like FileReader would be better off in DOMKit, which is in need of finishing, if you’re interested.
I agree, JavaScriptKit is only supposed to wrap APIs that are available across all JavaScript runtimes, including Node.js. DOMKit is a better fit for browser-specific stuff, and there we try to get these wrappers automatically generated. I don't remember if FileReader is covered by our codegen off the top of my head...
For example, would you accept a
JSFileReader
class, similar toJSDate
, which would wrapFileReader
?The text was updated successfully, but these errors were encountered: