Bug

In an Angular project Storybook is displaying this console error for a link generated by Compodocs

Warning: validateDOMNesting(...): <a> cannot appear as a descendant of <a>.
    in a (created by Markdown)
    in a (created by Markdown)
    in p (created by Markdown)
    in Markdown (created by ArgRow)
    in div (created by Context.Consumer)
    in Styled(div) (created b

相关平台

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)
• [

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

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 email generated for creating a new org does not say anywhere that you'll be creating a new org.

We should probably change:

• subject line -> "Create your Zulip organization"
• text above the button

Draft text (minimally different from current version):

You have requested

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