React Native

Describe the bug

Some community Storybooks were moved out of the monorepo some time ago. In the README file, the links which refer to them are broken.

To Reproduce

相关平台

微信小程序

复现仓库

https://github.com/yangxudong-functorz/taro_issues/blob/main/issue1.ts
小程序基础库: 2.17.3
使用框架: React

复现步骤

直接只用 npm run build:weapp, 报错: Module not found: Can't resolve '"},"path":"....../xxx.config.ts"

期望结果

编译成功

🚀 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 file ~/.config/joplin-desktop/log.txt is never rotated or truncated, and gets included in every Time Machine backup. The longer you've been using Joplin, the slower your backups run.

% cd ~/.config/joplin-desktop
% head -5 log.txt
2021-03-15 21:28:13: App: "Profile directory: /Users/jgreely/.config/joplin-desktop"
2021-03-15 21:28:13: "Database was open successfully"
2021-03-15 2

getPrepackagedPlugin throws an unrecoverable error when a plugin manifest specifies an icon path that doesn’t exist. But installing that plugin via the marketplace doesn’t throw the same error, instead just logging a warning. Let’s change this to have warn semantics instead.

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 

At present, we indicate places where a stream can be changed to a different one in a couple of different ways -- sometimes with a pencil icon, sometimes by just allowing the user to type into the box.

This can cause confusion, as inputting a non-existent stream name will cause sending or moving a message to fail.

We should make it clear that the user is selecting from a list of streams by u

facebook/react-native@1d92454 Adds 2 new events to <Text> - onPressin/onPressOut. We could add them too.

We should discuss/consider using baseUrl in our tsconfig so we can change imports like this:

import { Thing } from "../../components/thing"

to this

import { Thing } from "components/thing"

Docs: https://www.typescriptlang.org/tsconfig#baseUrl