Information-free types about github HOT 7 CLOSED

👍
Even this would be breaking change

from github.

Note that this can also be quite annoying if taken too far. It should be used in places where ambiguity is likely and highly problematic; I'm not convinced it should be done everywhere that is possible.

from github.

I'm not convinced it should be done everywhere that is possible.

Quite possible I don't feel this pain as much because I usually have iso, ala or coerce in scope.

from github.

Something is already done in http://hackage.haskell.org/package/github-0.14.0/candidate
Let's make more changes on need

from github.

@phadej what is it you believe disposed of this issue?

from github.

@bitemyapp unfortunately I don't fully know what you'd like to see for this issue. There are no plan, and something is already done.

If you really like to see something happen, please make a concrete proposal to be implemented. All endpoint (and their parameters) are visible at http://hackage.haskell.org/package/github-0.14.0/candidate/docs/Github-All.html. The better function type signatures would be a good conversation starter.

from github.

@phadej it's not to my usual preference, but this does seem to be a reasonable attempt at solving the discoverability/new user experience issues for the documentation.

Accordingly I'll stop agitating for now and see if anybody complains about the implementation.

Thank you for picking up the library 😄

from github.