Describe the bug
When story id starts with settings, the addon panel is frozen/broken/not responding. 🤯

https://user-images.githubusercontent.com/11510581/116053981-83f51f80-a67b-11eb-8a70-28e8b989b50e.mp4

To Reproduce
I reproduced it on newly created CRA with SB. See video above.

To reproduce: just add story id starting with settings

export default {
  title: "

相关平台

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

We are starting to migrate the mattermost-webapp over to TypeScript to facilitate better code quality. This Help Wanted issue is to modify components/invitation*modal/invitation_modal_guest*step and associated test files.

Below is a checklist of items you should be doing to migrate:

• < ] Rename the files to their associated TypeScript extensions (ie. js to ts, jsx to tsx)
• [

Current Behavior

the current DrawerItem passes accessibilityState to Link. this is an invalid attribute for role="link"

Expected Behavior

also exclude accessibilityState from Link in the default DrawerItem

all that really needs to be done is add a line under [this line](https://github.com/react-navigation/react-navigation/blob/0fce8eb2a1e682194d574c65f3366f72e23f2

The documentation for mutate talks about local mutation for faster feedback, but the documented way to use it only mutates after a promise has resolved - in other words, not immediately.

As a result, I've found myself writing code in this kind of pattern:

mutate(path, { ...data, patch }, false); // mutate immediately, don't revalidate
await patchData(patch); // await the 

The "src" directory contains a number of JS files that are added to the base copy of RN. It is not a complete source tree itself. Renaming to "patches" would increase clarity of intent, and follow OSS "patch-package" conventions.

Create an incoming webhook integration for Patreon. The main use case is getting notifications when new patrons sign up.

Patreon webhook documentation: https://docs.patreon.com/#webhooks

Now that Zulip has a Patreon page, it would be great to be able to monitor new sign-ups!

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