-
Notifications
You must be signed in to change notification settings - Fork 12
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
Published docs are wrong #8
Comments
Hi Joakin! Ha, i didn't notice that until just now. @casperin originally created the docs so i'm not sure what he used. I'd been watching ramda's doc discussion. Perhaps, i'll use what they decide on - doesn't really matter to me. I didn't place too much emphasis on the docs as they are just the standard ecmascript fn's with the object as the last arg. I do see the importance, however, and should up my game there. |
If we get to know what tool was used, I could try and make a pull request How do you feel about JSDoc comments? (I don't like them much, but it seems On Mon, Aug 18, 2014 at 6:35 PM, Brian notifications@github.com wrote:
|
I once wrote a processor to convert type signatures to jsdoc style comments. Maybe i'll try to find that... Any help would be much appreciated - I don't have any preference to a particular doc generator or style. I'll see if Gorm chimes in with what he originally used. He/we had been grabbing mozilla ecmascript examples and docs for the most part so I'm not sure how he got that going. |
I'm closing this for now, it's been 2 years. If there's more interest we'll reopen. |
Hi, I was looking at the library and looking at the docs, and the sidebar is all messed up.
Inside the Array header there are the array methods, regexp, object, number and string methods all mixed up.
From what I've seen there is no src for the docs, the html is hand edited. Whats the workflow with that? How do you generate the syntax highlighted code?
The text was updated successfully, but these errors were encountered: