-
-
Notifications
You must be signed in to change notification settings - Fork 209
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate documentation.js #37
Conversation
Current coverage is 100% (diff: 100%)@@ master #37 diff @@
===================================
Files 7 7
Lines 12 12
Methods 0 0
Messages 0 0
Branches 0 0
===================================
Hits 12 12
Misses 0 0
Partials 0 0
|
Let's 馃殺 this first thing @bhough! Can you review & merge? |
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.
One small comment @mxstbr
@@ -55,6 +55,7 @@ | |||
"babel-preset-latest": "^6.16.0", | |||
"cz-conventional-changelog": "^1.2.0", | |||
"docdash": "^0.4.0", | |||
"documentation": "^4.0.0-beta16", |
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.
Should we remove the JSDocs and associated Babel plugin as a dependency now?
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.
Arg yes we should, good catch! Mind doing that and pushing to the branch?
Remove npm packages leftover from previous JSDocs implementation.
This is so nice! Looks like a huge PR, but is actually much less code now since the theme is no longer inlined. I was able to remove almost all JSDoc comments (except for the examples) in favor of flow types, and documentation understood everything perfectly! 馃槺 So super cool!
This is what it looks like right now, which to be honest I quite like!
Whatcha think @bhough?
Ref: #31