Describe the bug
If the current day of the month the user is in is not available in the target month in the controls date picker, then it would not allow you to select the month. I noticed that the date picker was working fine yesterday (1/28) when I need to select 2/5 for the view and then today (1/29) when I try to select 2/5 it would automatically switch to 3/5.

To Reproduce
Steps

相关平台

微信小程序

复现仓库

https://github.com/li-z/taro-bug
小程序基础库: 2.12.0
使用框架: React

复现步骤

运行项目后点击跳转到详情页，然后返回首页。然后触发子组件的 onClick 事件时，回调函数却还是详情页的函数。去掉id属性后正常。

期望结果

有无id属性都应正常

实际结果

有id属性异常

环境信息

Taro CLI 3.0.7 environment info:
    System:
      OS: macOS

🚀 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

I believe this would address at least part of the use case for the broader issued described in #17137.

It's probably a pretty simple change, as we already have tackled this in the "Private Messages" section--you can ask buddy_data and similar code pretty easily to get what you need to render the green/orange circles.

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