Helm documentation states the following:
-1) (k8s) metadata.name is restricted to a maximum length of 63 characters because of limitations to the DNS system
-2) For that reasons, release names are (DNS labels that are) limited to 53 characters

Statement 1) is not correct.
k8s does not impose a max length of 63 characters on resource names.
The actual max length for a resource name is 253 c

We would like to avoid confusion like we have in webpack-contrib/webpack-bundle-analyzer#185

We could document statsFilename and reportFilename options allowing the use of an absolute file path like /path/to/folder so that people would know it's supported.

Let us know in this issue if you would like to contribute to this!

Is your feature request related to a problem? Please describe.

It is idiomatic for JWTs to be accepted using a header format of Authorization: Bearer <JWT> (see jwt.io introduction.) In general, in history, the RFCs surrounding the authorization header have taken care to specify the mode of Authorization as the first part of the header value (e.g. Basic, Di

The y-axis ticks supports the rotated option, but the doc is missing.

I haven't checked whether other options are missing.

一般情况，单元格JSON数据：
{
"ct": { //单元格值格式
"fa": "General", //格式名称为自动格式
"t": "n" //格式类型为数字类型
},
"v": 233, //内容的原始值为 233
"m": 233
}
里面的内容是保存在v里面的

而多行文本的内容却保存在ct里面的s里面的v里面，JSON结构如下
{
"ct": { //单元格值格式
"fa": "General", //格式名称为自动格式
"t": "inlineStr" ,
"s":[{"v":"多行文本\n多行文本"}]
}
}

这两种单元格的JSON结构都不一致呢，导致websocket后端保存数据 update

Hi, I'm creating a line chart with values between 20 and 80, and I would like to limit the y axis to this values.

The current graph shows the y axis scale from 0 to 80.

Is possible to set yaxis limits from 20 to 80?