Documentation needs to clarify relationship between various rules. about rules_proto HOT 2 CLOSED

Point taken. I've tried to take the approach to generate an example WORKSPACE and BUILD.bazel file that demonstrates a functioning / buildable example. However, documentation on the individual rule attributes needs some attention.

Here's the basic idea:

1. Always start with a native proto_library rule.
2. If you only want to the generated source code artifacts, use a {lang}_proto_compile rule. deps always point to proto_library rules.
3. If you want the code artifacts "compiled" or incorporated into some {lang}_library rule, use the {lang}_proto_library rules. deps also point to proto_library rules. For this class of rules, there should be an escape hatch to provide additional language-specific deps if necessary, like for example py_deps that would be passed to the py_library.deps attribute. This convention is currently lacking but it usually not necessary since most people keep their proto rules independent of their application specific code.
4. If your proto has services, use a {lang}_grpc_{compile|library} rule instead.

from rules_proto.

Should be addressed by #9. Feedback welcome.

from rules_proto.