-
-
Notifications
You must be signed in to change notification settings - Fork 29
What is the expose format? #58
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
This is intended for stuff like |
It's not though. window.HTMLImageElement !== window.Image. window.Image is a useful factory function, whereas window.HTMLImageElement throws. |
Right, I had hoped that this would be somehow possible, maybe my having an |
Hmm, I see, that makes sense. So in the future we'll do something like expose: {
Window: {
HTMLImageElement: HTMLImageElement,
Image: Image
}
} where |
Well, I'm not sure about the generated wrapper part (seems like a recipe for circular dependencies, since namedConstructor_Image would need to use one of the create functions from the generated wrapper). But the general idea makes sense. So let me close this and update #60. |
Support namespaces
That is, why is it
instead of
and then we know the thing to expose is the
interface
export, and then name to expose isinterface.name
?The text was updated successfully, but these errors were encountered: