Improve fp doc generation #1963
This is a follow-up to the work done in #1897, and adds a lot of changes to improve the signature of the methods and the examples in the generated docs.
There is still a few things to do/fix (also listed in the gist, including converting the tests I wrote to QUnit), and ultimately, some examples will have to be adapted (either in this PR or later) because they won't make that much sense. For example:
Anyway, I was told it would be nice to share my progress, so there you go ;)
2 times, most recently
Feb 9, 2016
Ok, well, I think I've ended at a somewhat pretty satisfying point. I've done all the improvements that I currently could think of.
Current pain points are all the examples that are still broken, mostly because the examples given don't make sense in FP:
Agreed, but I'm sure some examples could be rewritten so that it works in both modes, but this can be an ongoing process.
Do you have any idea on when this could get published on the website? Waiting for lodash/lodash.com#8 to advance?
Thanks for merging the PR, hope you like it, and let me know if you want some improvements on this part :)
I'll clean it up this go around. I imagine the bump after next will see it. I generate our current docs by pointing its markdown to html converter to a https://rawgit.com of a gist of our documentation. I could do the same for the fp docs (not a ton of work there).
Beyond this I'd dig entries in the build-differences or a separate wiki just for fp.