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
ES6 modules export { var1, var2, ... } doesn't work. #259
Comments
To reproduce, add
to the https://github.com/TypeStrong/typedoc/blob/master/examples/es6/src/es6.ts Generate docs, and see that Foo doesn't appears in "exported". Really bad bug. Making the tool unusable. I hope that's me doing something wrong. |
People, seriously, please help. Is it really possible to use TypeDoc without that? Can someone investigate the issue? |
@gaperton I'm sorry that you are having trouble. You should know that this project is only maintained by volunteer effort from the community. There is no one dedicated to resolving issues. I tried adding |
Just made clean install of the TypeDoc, done Added Could you please confirm again, that you don't have such a problem, and tell me which TS compiler version are you using? Mine is 1.8.10. It becomes huge problem with 'barrel' modules, as they contains a lot of re-export directives. |
Ah, I missed that you were filtering that checkbox. Okay, I can reproduce this. I exported the JSON. You can see that the isExported flag is not set for "children": [
{
"id": 28,
"name": "DataService",
"kind": 128,
"kindString": "Class",
"flags": {
"isExported": true
}
},
{
"id": 18,
"name": "Foo",
"kind": 128,
"kindString": "Class",
"flags": {},
"children": [ If anyone is interested in trying to address this. I'd first look at declaration.ts |
It doesn't get there for https://github.com/TypeStrong/typedoc/blob/master/src/lib/converter/converter.ts#L366 node.kind is 231. TypeDoc just ignores it. |
So, looking at the sources, only simple assignment exports support is implemented. Other exports directives are ignored. Too bad. Flag 'exported only' is useless, so there must be other way to hide private declarations. Is there some way? |
Okay, for everyone who are interested in workaround. Use |
m
is not exported in this example. But should. As result, I cannot use TypeDoc for in my libraries, thus, severity 'critical'.Could we do something about it? May be I'm doing something wrong?
The text was updated successfully, but these errors were encountered: