mirror of https://github.com/grpc/grpc-java.git
a206cda1a8
Users appear to be doing `attributes.toString()` to find keys they are interested in and then unable to find the name of the Key in our API. They workaround the problem by scanning through `attributes.keys()` looking for the key of interest. This is an abuse of the keys() API and unnecessary user friction. They'd happily use the API if they just knew where to find it. I added internal to some strings to make it clear that you shouldn't go looking to use it. There were many strings I didn't change. I focused on keys most likely to be seen by users, which meant keys in grpc-api and keys that are available via transport attributes. See https://github.com/grpc/grpc-java/issues/1764#issuecomment-1139250061 |
||
|---|---|---|
| .. | ||
| generated/main/grpc/io/grpc/alts/internal | ||
| main | ||
| test/java/io/grpc/alts | ||