如题，有时重新翻文档时突然发现某些地方更新了。

相比版本更新的很多内部优化，但凡文档更新大都是需要开发者关注的。
当某天重看文档时，面对一篇几千内容的文档，一段重要内容的一行文案变更，或者某个大类的角落摸摸增加了一小段子类目，实在难以查别

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

Hello!

Reactotron provides nice feature of exporting whole API calls to markdown, which I've noticed recently and started using heavily to communicate bugs to backend developers.

Would be great if those markdown exports also included local timestamp, as it'd allow backend developers to correlate my logs with theirs. It's especially important for timeout cases where I don't have any of their

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 

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

Current behavior:

When I add

declare module '@emotion/react' {
  export {Theme} from 'somewhere';
}

typings for theme prop is correctly set, but whenever type of styled(Element) becomes StyledComponent<any, {}>. If I remove the above declaration, the type of styled(Element) becomes

StyledComponent<Props & etc>

which is correct.

Al

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?

Just a FYI when people start trying to submit bugs about this, mobx-react shipped a funky build which is causing broken-ness (at least when using redoc-cli bundle)

mobxjs/mobx-react#831

Currently breaks with an error like:
Cannot find module '..../.npm/_npx/1868/lib/node_modules/redoc-cli/node_modules/mobx-react/dist/mobxreact.js (added for searchability)

Can

Question

Hey guys, I just wanted to get started with spectacle, but the docs are confusing me quite a bit.
These are the issues i am having:

1. "Getting Started with Development" - this paragraph tells me, that all my source files have to be inside the src/ dir. So far so good. But this also reads a bit like there should already be such a directory after installing spectacle with `yar

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

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.

Not a bug per se, but a clarification seeing that the docs aren't very up-to-date. If you need to set focus on the editor on render (e.g. on first page load), with functional components you can do it like this:

import React, { useRef, useEffect } from "react"
// other stuff

const editorReference = useRef();
useEffect(() => {
  editorReference.current.focusEditor();
}, [editorReferen

https://emotion.sh/

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

Versions

What is the expected behavior?

In Modal header, close button icon is not showing after build but it was visible is localhost

What is the current behavior?

W

Opening this issue in case anyone wants to help. Recently, we've configured Storybook to import files from __examples__ folders inside Reakit component folders. This is how we're doing it:

https://github.com/reakit/reakit/blob/0b70f435673db13b75f82d69ac2760b485879674/.storybook/preview.js#L7-L22

Thos

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';