Fix JS prototype chain for exported .NET subclasses #368
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #365
JSClassBuilder
constructorbaseClass
parameter when defining a subclass.instanceof
work as expected for instances of the exported classes.ModuleGenerator.cs
to ensure the base class was separately declared as a variable before constructing the subclass. Previously the entire module was declared as one chained statement; now each type is declared and added in separate statements.version.props
file is generated bydotnet pack
.