-
Notifications
You must be signed in to change notification settings - Fork 42
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
Have tsd-jsdoc generate default exports #98
Conversation
Still buggy: module declaration is generated twice.
…t' doclets. => fixed: generation of 'export default' at the end of the module (and not at the beginning) => fixed: duplicate module declaration
module2 test addition.
`debug()` controled by a specific `debug` option.
'documented' => by default 'exported' => not fully implemented, just prevents non documented doclets to be removed for the moment
cherry-pick & merge from @HackbrettXXX's commit 312578e
From [PR#74](englercj#74) with fix.
Lots of them are not enabled yet and need to be fixed.
Fix for 'module.exports = {name: }' pattern.
…ass would actually).
…neration strategy. Warn&debug improvements.
Instrumentation for jsdoc 3.5.5 vs 3.6.3 investigations.
# Conflicts: # package-lock.json # package.json # test/expected/class_all.d.ts # test/lib/index.ts
Status on this PR. At this time, all tests pass successfully, either in Brings improvements and fixes, in particular for the following:
What remains to test/do:
|
@Alexis-ROYER, Have you had a chance to revisit this now that the holidays are passing behind us? |
Hi @englercj, sure, it has been a while since the last status... Here's an update:
This is on the way, but as I've been busy on other things, I must admit it has been delayed. I let you known as soon as I get back to it. |
I eventually managed to get it done. Just for the story: while integrating That's the reason why I went through a dedicated study (see tsd-default-export). This study brought to formulate recommendations on default exports, which recommendations I have applied in commit 1ac9c2c, Apr 2020. Status on this PR:
Note on the exported generation strategy: requires a Ready for review. |
Awesome! Thanks for all the hard work @Alexis-ROYER. I'll take a look at this today. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, thanks again for this PR @Alexis-ROYER. This is a great change.
All my comments were stylistic, and I tried to add suggestions that can be added in directly for most of them. Thanks again!
'exported' tests were not executed due to a false trailing 'r' after `generationStrategy` in `test/lib/index.ts`.
@englercj I think I managed to fix all the points so far. Let me know if you have any more questions or remarks. |
This was awesome @Alexis-ROYER, thanks again for all your hard work! |
My pleasure. |
I'm starting a draft PR for issue#96.
Still work to be done on it, but I share the code right now so that one could review it and give me advice on how to lead the things.