Describe the bug
When applying a dark theme to the Docs page, the table still has white and light gray background colors. This obviously ruins the readability of the table as the text color is also a light gray. There is a hardcoded background-color: white; value applied to the table tr element.

To Reproduce
Steps to reproduce the behavior:

1. Use a dark theme for the docs page

相关平台

H5

浏览器版本: Mozila/5.0 （Linux；Android 9；V1938CT Build/PPR1.180610.011; wv） AppleWebKit/537.36 (KHTML，like Gecko)Chrome/62.0.3202.84 Mobile Safari/537.36 VivoBrowser/8.2.16.1
使用框架: React

复现步骤

在此系统自带的浏览器上, 随机无规律(暂时没找到规律) 部分element显示, 部分element不显示, 刷新后出现的问题也是一致, 在其他手机上(如iphone 6s ios13.3 iphone XSmax 13.6 小米...)

🚀 Feature request

Current Behavior

The type ErrorMessage doesn't have an id property.

Desired Behavior

It'd be nice id?: string would be added to the type ErrorMessage and set on the outermost component that serves as error message.

Suggested Solution

Add id={this.props.id} to the outer component in ErrorMessage.

Who does this impact? Who is this

Currently, the Ctrl+Shift+B shortcut is assigned to focus the note editor. However, when the current layout is viewer-only, it doesn't make sense to focus the editor. Instead it should focus the viewer panel.

Summary

The intent is that the API for the client config return values that are logically boolean as JSON values true or false rather than string values "true" or "false".

Steps to reproduce

Request the client config from the API:

curl 'https://community-daily.mattermost.com/api/v4/config/client?format=old'

Expected behavior

Values are returned

Related: react-navigation/react-navigation#8160

We have a similar guide for React Router + Netlify https://github.com/expo/examples/tree/master/with-react-router#deploying-to-netlify

We should also have one for Now:

• Create now.json:

{
  "version": 2,
  "routes": [{ "handle": "filesystem" }, { "src": "/.*", "dest": "/index.html" }]
}

A bit of context, we introduced swr two weeks ago to our codebase. Everything is working fine, but we started to get some reports about some parts of the app being broken in slightly older browsers (Chrome 49, Firefox 59, Edge 18, etc…)

We found out that swr was causing a syntax error in these browsers because webpack by default picked the ESM build (rightly so) but because it's not transp

If you send the message:

```
real	0m0.322s
user	0m0.344s
sys	0m0.036s
```

it turns into:

```
real 0m0.322s
user 0m0.344s
sys 0m0.036s
```

when it goes through the server-side markdown renderer. The local echo looks fine.

...this boilerplate is awesome, thank you for sharing it guys 👍