Skip to content
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.

Fill out Usage section #36

Merged
1 commit merged into from
Jan 7, 2017
Merged

Fill out Usage section #36

1 commit merged into from
Jan 7, 2017

Conversation

RichardLitt
Copy link
Member

While I could list all of the available methods, I think that the GoDocs already do this fairly well and I would be duplicating data. However, a tracking issue with all of the methods that are needed would be ace. Shall I set one of those up?

I also point to the spec here. If someone points me to a Go package with a good Usage and API section, I am happy to fill this out more; however, I am not sure how else to best go forth with filling this section out.

Related to #13 and #15.

While I could list all of the available methods, I think that the GoDocs already do this fairly well and I would be duplicating data. However, a tracking issue with all of the methods that are needed would be ace. Shall I set one of those up?

I also point to the spec here. If someone points me to a Go package with a good Usage and API section, I am happy to fill this out more; however, I am not sure how else to best go forth with filling this section out.
@RichardLitt
Copy link
Member Author

@whyrusleeping Thoughts on this?

@whyrusleeping whyrusleeping added the status/in-progress In progress label Sep 14, 2016
@whyrusleeping whyrusleeping added status/ready Ready to be worked and removed status/in-progress In progress labels Nov 2, 2016
@ghost ghost merged commit e9fa57e into master Jan 7, 2017
@ghost ghost removed the status/ready Ready to be worked label Jan 7, 2017
@ghost ghost deleted the feature/usage branch January 7, 2017 00:06
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants