Update jsdoc-to-markdown to version 2.0.0 🚀 #72
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.
Hello lovely humans,
jsdoc-to-markdown just published its new version 2.0.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of jsdoc-to-markdown.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
This release is intended to freshen up the codebase and make a few improvements while longer-term goals continue to be developed. The majority of improvements relate to performance, the API and dependency tree cleansing - the data and rendered docs output are largely unchanged. For now.
Breaking since 1.3.6
sourceoption added, you can now pass in source code as a string.--namepathsreturns all namepaths found in the supplied code--sourcetakes source code in as a string. Useful in scripting.--jsdocreturns the raw, unchanged jsdoc data.--clearclears the cache--no-cacheskips the cache--version-cis now the alias for--configureinstead of--member-index-formatto match the jsdoc-coption.--confoption renamed to--configureto match the jsdoc--configureoption.--srcoption renamed to--filesto avoid confusion between--srcand--source--sort-byand--group-byremoved for now, back in a future version or by popular demand.kind(likemember,classetc.) not doclet property, as before. TheisEnumproperty in the--json(and jsdoc-parse) output has gone.@privateand@ignoreddoclets and are now left in the--json(jsdoc-parse) data, and filtered out at template (dmd) level instead.Other updates
Dependency tree
Old package and deprecation warnings should now be gone.
Documentation
Fresh tutorials in the wiki, more to come.
Usage stats
I'm curious to know whether i can drop node 0.10 or 0.12 support. Also, i'd like to know which features are used/unused, need improving or better documentation. So, the tool keeps count of the features and node versions used. Only count totals are sent, no data, filenames or source code.
To disable collection of stats, run this command:
jsdoc-parse changes
dmd changes
The new version differs by 149 commits .
d9fb19b2.0.010ff1b3readme97ac0a6readme24025b4more testsa4530a02.0.0-alpha.23de7f688deps.. jsdoc now receiving correct cache option0f47f2dswitch 'cache' option with 'no-cache'.. guaranteed exit.. linting, more tests25dfd18readme5536e3bAPI docsc2e3185merge in nextad3e9e7deps8458398docsf8edb4cdocse4ab2702.0.0-alpha.224d76a79correct module.exportsThere are 149 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade