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
please q. why no api document ? #438
Comments
We could maybe make a community documentation. |
I'm on the fence on this one. Btw. I just fiddled with this oneliner:
Which produces the following:
Perhaps we can categorize them a bit, comment on them, and add them as markdown tables to README.md, something like: EventsYou can add functions to nodes to respond to certain events:
Other thoughtsWe could also just publish the
|
An action would be great. Currently I automatically build the docs for my fork (only used to publish current npm packages) and it would also have to run ./utils/generate_doc.sh. The output is published here: https://inamataco.github.io/litegraph.js/ |
This will make the development become difficult, even if it can be developed now, but the maintenance cost is still high in the later period, if the member changes, the new member will re-learn.
I hope that an official api document can be issued, which will make developers more favored. Thank you!
The text was updated successfully, but these errors were encountered: