Is your feature request related to a problem? Please describe
In my component's props TS interface, I can use JSDoc comments to set the description, and can even use the @default tag to describe the default value 💯
However, nothing happens when I use the @deprecated tag.

Describe the solution you'd like
Some ideas:

• It would be nice i

相关平台

微信小程序

复现仓库

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

The documentation of all components lists the props as well as their usage. It would be great if we arrange the props list alphabetically to make it easier to find the required props.

Just like the expo docs and others.

Proposed Fix
The docs are written using markdown and can be found [here](https://github.com/react-

Help contribute to the Incident Management Plugin!

Today, running /incident info from within a non-incident channel shows the following message:

You can only show the details of an incident from within the incident's channel.

Let’s change this to:

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.

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" }]
}

In the use-swr file, I found some effect dependencies not exhaustive, I want to konw it is correct or not.

If add eslint-plugin-react-hooks, and add "react-hooks/exhaustive-deps": "warn" in your .eslintrc It will w

There are a number of calls in zerver/views/auth.py to get_realm -- and most, but not all, catch the potential Realm.DoesNotExist exception that that raises. The ones that don't currently should catch the Realm.DoesNotExist and raise a JsonableError, to prevent 500's like this:

$ curl -sSX POST https://invalid.zuli

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