-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add a blub to README about running YACE as a library #34
Conversation
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.
Left some tiny nits, looks good
README.md
Outdated
### Embedding YACE as a library in an existing application | ||
It is possible to embed YACE in to an existing library to scrape on demand. This might be useful to you would like to scrape on demand or run in a stateless manner. | ||
|
||
The entrypoint to use YACE as a library is [update.go](./pkg/update.go) which requires, |
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.
Maybe worth mentioning the entrypoint func, rather than file name (or both?)
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.
A link to GoDoc here may also be nice
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.
A link to GoDoc here may also be nice
Good call, I should probably add a GoDoc as well
a0d8d07
to
311140c
Compare
311140c
to
dbbc462
Compare
Thanks for the feedback, upstream PR is open nerdswords#560, I'll close this and will sync it with upstream when it comes through. |
Looking for some feedback on this before I submit it upstream with the metric registration changes. I'm not always the best at writing coherent docs.