Server interface names not conforming standard-naming about rest HOT 4 CLOSED

The interfaces are only used to allow calling resource methods in a dynamic like way without resorting to full reflection. They probably shouldn't be public, but then godoc readers wouldn't have been able to find the signatures of the methods their resources needed to have. The only use I can see for the interfaces to a programmer using rest.go is documenting the method signatures that can be called if they are implemented. As such, the interfaces would never be used in place of an actual type (that being the actual type created to implement the resource) such as io.Reader, where that naming convention makes sense.

Also, some of the names become weird. For example the Options interface would become Optionser.

So, if you have an example where the interface name is used outside of the rest.go core code, and have suggestions on how to rename them (or possibly the functions they require) I am happy to consider the suggestion.

Nathan

from rest.

Ok, thanks for pointing that out.
I/We’ll see about that.

from rest.

I have made those interfaces private and wrote better documentation to highlight the methods that can be called.

from rest.

I especially like the new README.
Documenting how to use rest.go was what I was looking into as well. :)

from rest.