问题描述
最近使用movable-view做了一个拖拽排序的功能，但是由于需要touchmove事件频繁setState来更新movable-view的坐标，导致Android的上的性能体验很差，IOS不会。

看了微信的文档，这种情况可以使用WXS来解决，请问Taro中能否使用WXS？如何使用呢？

参考文档: https://developers.weixin.qq.com/miniprogram/dev/framework/view/interactive-animation.html
https://developers.weixin.qq.com/miniprogram/dev/framework/performance/tips.html

Too wide (and falsy) segregation of GraphQL Types and Resolvers

The first example of this is new ObjectType in src/data/queries/index.js importing fields.
Fields should be taken in context of parent type, not as standalone information.

This can ensure some users that custom types cannot have own field resolvers which is false.

In fact, much of fields which can have own resolvers

Repro

Here's my repro case:
https://jsfiddle.net/sethwieder/L46en8b2/40/

Expected

We're passing in an object as the input and expected it to denormalize nested objects based on the provided schema.

Actual

The output duplicate the same item for each index in the input array.

Context

This used to work in 3.2.3, but no longer works as of 3.2.4.

It's unclear to me if t

I have issues to get Reactotron working in my jest react-native test environment.
Before running a test I simply do
jest.mock("reactotron-react-native");, but then I receive an error stating
TypeError: Cannot read property 'useReactNative' of undefined
![Screenshot 2019-08-09 at 18 01 26](https://user-images.githubusercontent.com/16821682/62792504-bd64b080-bacf-11e9-96a8-0d33089332ac.pn

Based on the description. If project owners are ok enable Stage 2 Babel transformation it is a good alternative to bind in the constructor.

class Switcher extends React.Component {
  constructor(props) {
    super

I have a component with types and jsdocs:

export type ButtonProps = {
  /**
   * explicitly toggle loader on and off
   */
  loading?: boolean;
} & React.ButtonHTMLAttributes<HTMLButtonElement>;

/**
 * Base button, with very basic styles. Accepts all parameters of native html button.
 * If onClick returns a promise, BaseButton will show a loader automatically, until the promise is 

Hi, i'm looking to use Emotion to style a react ui library (as a peer dependancy) and couldn't find any docs specific to this use case?

The docs talk about both emotion and @emotion/core but have left me a little confused as to which is preferred when using it in a codebase that will be consumed by another applications build step and what implications this might have when the consuming app

I didn't see any way to send this feedback from the website, so I'm posting here as an issue.

The installation docs lists the following clone url:

https://github.com/coreui/free-bootstrap-admin-template.git

when in fact it should be this repo's url:

<https://github.com/coreui/coreui-free-bootstrap-admin-template.g

Reading readme.md, the point "📓 Speaker notes" (the link is broken) is a feature that exists, no longer exists or a mistake?

We recently upgraded from RC8 to RC23 (to resolve the sidebar scrolling issue.) We noted that our examples which had originally, appeared like this:
Example: page[number]=1&page[size]=10
now appear like this:
Example: page=page[number]=1&page[size]=10
It would seem this line:
https://github.com/Redocly/redoc/blob/v2.0.0-rc.23/src/utils/openapi.ts#L333
causes the issue.
Is there a way to sto

We should use https://github.com/jonschlinkert/parse-github-url to intelli

We should upgrade to react-static v7 to reinstate hot-reloading to make doc development less painful.

There are a number of breaking changes we'll need to address upgrading from v5.9.12, including upgrading babel and deprecating our use of a couple plugins.

This should be considered a future improvement

Is your feature request related to a problem? Please describe.
gdb features, such as whether reverse debugging is enabled, is currently guessed at by gdbgui.

Describe the solution you'd like
use -list-feature instead of guessing gdb's features

https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Su

Describe the bug

In local development mode, modification is not applied

Dejavu Version
Your version of Dejavu and how you're running it: Web, Chrome Extension or as a Docker Image.
Web, current master version. (git clone)

To Reproduce
follow https://github.com/appbaseio/dejavu/blob/dev/CONTRIBUTING.md

I managed to connect to the local running server.

However the code

Is your feature request related to a problem? Please describe.
It's hard for some Chinese developers to read English documentation.

Describe the solution you'd like
Add Chinese documentation.

#509

I see that there is documentation on various webpack/babel configuration but the building process is missing from documentation. Wouldn't it be better if there's a couple of paragraphs added to the docs to go over the build process?

Expected Behavior

Using a line break or new line entry (shift-return or return) carries over to the invoice preview and generated PDF as displayed in the invoice creation view.

Current Behavior

Le bug.

The demo on https://fkhadra.github.io/react-toastify/ contains this:

while it should be:

since the former doesn't seem to be a valid property anymore.

Related

Apollo has something called schema-link, which allows queries running on the server to execute against schema locally, instead of passing the request through HTTP back to itself.

Just curious if urql has an exchange to support that pattern yet, or if there are any plans for it?

Thanks for a great lib!

https://github.com/FormidableLabs/react-game-kit/blob/e9797f473913a67efe17fae2ed1b991d2508d53e/src/components/loop.js#L38-L48

Since Loop doesn't say anything about rendering, maybe we could change this div to React.Fragment?
I'm happy to make a PR if it's okay.

If I add editorState and mention together it breaks the editor

`<Editor
toolbar={toolbar}
editorState={editorState}
onEditorStateChange={onEditorStateChange}
mention={{
separator: ' ',
trigger: '@',
suggestions: [
{ text: 'APPLE', value: 'apple', url: 'apple' },
{ text: 'BANANA', value: 'banana', url:

https://emotion.sh/

After this change in Material UI: mui-org/material-ui#6115

🚀 Feature request

Motivation

Similar to Reach UI, if the project declares what screen readers and browser combinations are tested, it gives adopters confidence that the components take into account different screen reader quirks to deliver the best UX.

Example

Quote from Reach UI:

Each component is tested with Safari + Voiceover, Firefox + NVDA

Change how component imports look like in Storybook stories. Instead of this:

we should display this (because that's how end users access our library):

import { Checkbox, Fieldset, Toolbar, Button, Cutout } from 'react95';