-
Notifications
You must be signed in to change notification settings - Fork 118
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
type-compiler produces empty ops for some types and broken output #352
Comments
Yeah oxide.ts was not built using the type-compiler, so all their types will be excluded. In your case this results in an error since excluded types are not handled as |
Taking a types from third party npm modules would be helpful.
maybe it possible to build type declaration reflection for external modules by adding an extra type for this purpose?
|
Yeah that's not possible due to technical restrictions |
@marcj thanks for your help :) |
type-compiler produces empty ops for type
Result
from https://github.com/traverse1984/oxide.tscauses broken output:
with error
'Const declarations' require an initialization value.
Result
is both type and a class constructor.It happens because of
extractPackStructOfTypeReference
calls forextractPackStructOfType
with nodeFunctionDeclaration
, that stops working because ofconfig.mode
isnever
.I suspect it happens because of
findReflectionFromPath
readingtsconfig.json
from oxide.ts inside node_modules folder, and returns never cause there is no reflection field.The text was updated successfully, but these errors were encountered: