Adding the +build appengine tag made the docs disappear about go-endpoints HOT 5 CLOSED

Yeah, apparently it's a known issue: golang/go#3398
What shall we do?

@maxhawkins

from go-endpoints.

Yikes. That's no good.

I suppose we could put the public interface in files without a +build tag and delegate to appengine-specific implementations behind the tag. Do any of the public functions take appengine.* types as parameters?

In the meantime I suppose it makes sense to revert my PR.

from go-endpoints.

Unfortunately at least one exported function returns a user.User which means we are bound to appengine and I'm not sure we can analyze appengine depending packages from godoc.

I agree we should revert the PR adding the build tags

from go-endpoints.

For some side context from someone who's dealt with Endpoints and the user.User object a lot: You should not feel bad about axing it from the library.

For the long history of annoyance see the issue and for a description of the quirks, see a StackOverflow answer from me.

Take this as an opportunity to

1. Make the docs build happily and easily with the build tags you want
2. Drop the unnecessary "problems" discussed in #52 and #53
3. Inform users to stop using the App Engine User ID and start using the Google User ID. (I'd imagine most codebases already have custom user classes, so this inconvenient "convenience" of returning a user.User is all around not worth it.)

😬

from go-endpoints.

This is a bug in godoc.org, which @adg will fix.

from go-endpoints.