Scope: contribution from the community.

Description: It would be much helpful for the contributors to have a common and guiding template for creating issue. I know this is kind of egg and chicken problem that this issue is being created to create a proper issue. Anyway, I know it is quite trivial to create a Template for issue from setting interface. Just need someone to do it.

**Ass

比如Modules中的gg、gl、glm、gx等，太过简略，不能让人一目了然，再比如time下的time_lin.v，如果不是在特定情况下，很难联想到lin即指linux。
对于缩写，应该更多借鉴Go，而非Rust，首先在清楚无歧义的情况下其次考虑适当简写。

英文大牛帮忙翻译，[抱拳]

mapbox-gl-js version: 1.3.1

browser: *

Why scale control uses different earth radius than mercator projection code? Is this ok?

https://github.com/mapbox/mapbox-gl-js/blob/2020f3f9ced516086508925411bd098fbb4c3234/src/ui/control/scale_control.js#L130

https://github.com/mapbox/mapbox-gl-js/blob/2020f3f9ced516086508925411bd098fbb4c3234/src/geo/mercator_coordinate.js#L9

It seems that the official Javadoc is not up to date. I found differences in the latest releases and Javadoc site -> https://developers.google.com/protocol-buffers/docs/reference/java/.

I checked for UnsafeByteOperation.java at Javadoc site and at [github repo](https://github.com/pr

提交 Issues 请提供

1. 提供发生错误的步骤，最好有 GIf 动图
2. 异常日志（尽量详细，异常日志可以使用MD语法）

对于没有提供详细日志的 Issues 将直接关闭。谢谢

 We have a pilot redesign of the [AWS SDK for Go API reference documentation](https://docs.aws.amazon.com/sdk-for-go/v1/api/gosdk-apiref.html). Let us know what you think.

from https://raw.githubusercontent.com/aws/aws-sdk-go/master/README.md

Present a Webpage with the email [email protected] which doesn't work.

Current behavior:

Currently, specs-listing window is very bright:

Desired behavior:

Would it be technically possible to make a dark mode for it?

Description

So our function arrayToHtmlList is in a pretty bad space and could use an update. We already had some discussion over at #675 but I wanted to move the update discussion over to an issue for more visibility.

Current problem:

It uses an awkward query selector instead of the `document.prototype.getElementBy

As requested in #2626, we should document all the fields available via the context as they are not really discoverable. The doc should include grpc functions like SetHeader/Method/etc as well as fields stored directly within the context like metadata and peer info.