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

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

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

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

This is quite similar to #532 and #544. But different from those, it is happening with a present and valid value for the type attribute of the input element.

• @testing-library/react version: 9.4.0
• react version: 16.9.3
• node version: 8.17.0
• npm (or yarn) version: npm 6.13.4
• material-ui/core 3.9.2

Relevant code or config:

        <TextField
          typ

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

Description

Bit does not generate docs for React TS components.

for example:

https://bit.dev/eden/react-ts-demo

Specifications

• Bit version: 14.7.4
• Node version: 10.15.3
• npm / yarn version: 6.4.1 / 1.16.0
• Platform: macOS
• Bit compiler (include version): bit.envs/compilers/react-typescript@3.1.44
• Bit tester (include version):

Context and additional inf

Would be great to provide a documentation section with practical examples on how we propose to handle various popular patterns which usually are solved by pseudo selectors, nested classes etc.

Guys, help me, please!

So, i'm get this error when i run "ng build".

ERROR in node_modules/@coreui/angular/lib/sidebar/app-sidebar.service.d.ts(6,20): error TS1005: ';' expected.
node_modules/@coreui/angular/lib/sidebar/app-sidebar.service.d.ts(6,55): error TS1005: '(' expected.
node_modules/@coreui/angular/lib/sidebar/app-sidebar.service.d.ts(8,18): error TS1005: ',' expected.
node_modul

I created a theme:

https://github.com/pedroapfilho/mdx-deck-theme-awesomeness

And it was very fun. We should have a tool like create-react-app or create-next-app, but to create themes for mdx-deck, like create-mdx-deck-theme.

I can even create it. What do you guys think?

This is a feature request.

Would it be possible to change the default example value for the integer type?
Right now the default is 0, but since an integer is usually an id, it often makes more sense to use 1 in the examples.

Right now, the workaround is to specify the example every time an integer type is defined.

Not sure if this feature request would make sense for other types

Maybe we consider removing / replacing Deploying with Github Pages section at http://127.0.0.1:3000/docs/advanced-concepts/#deploying-with-github-pages

There seem to be a lot of undocumented assumptions about how you integrated your spectacle presentation and there are lots of deploy options. Might be better to do a spectacle-boilerplate-based deployment tutorial? (Or do that in `spectacle-

Add a field on the breakpoint that shows the number of times a breakpoint was hit. See The -break-list Command.

using: Docker
version: 1.5.0

Context

Filters are currently defined by clicking the table header 'filter' icon and then specifying the filter by a popover.

Feature request

Allow users to right click a field value in the data table and then filter by that value (e.g. '>', '<', '=<', '=>', '=', '!=').

Example screenshot

An example of this feature can be seen in [DBeaver](https://db

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?

Is your feature request related to a problem? Please describe.
We need to find the source code manually when reading the docs;

Describe the solution you'd like
Direct link to the components source code should be available on it's page at documentation.

Prerequisites

• We realize there is a lot of data requested here. We ask only that you do your best to provide as much information as possible so we can better help you.
• Read the contributing guidelines.
• Ensure the issue isn't already reported.
• Should be reproducible with the latest version of Manta.

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

I've spent some time playing with react-game-kit and did reproduce several examples from the official matter-js repo. The single demo currently commited in the repo is really nice but makes it quite hard to build basic things like gravity demos.

Would be great to have basic shape elements, like a Rectangle, a Circle that can easily be drawn into the dom.

Using SVGs is quite easy, properl

Add a GraphQL mutation that will be used on the Contact Us page and Send Feedback modal dialog. For example:

mutation {
  sendMessage(type: FEEDBACK, message: "Hello world!", email: "user@example.com")
}

See

• src/mutations/SendMessage.js
• src/server/mutations/contact.js

Bonus points for making it work with Firebase reCaptcha.

For now, I have created a custom toolbar for CodeMirror. Now How to change Editor box into code mirror editor?

🚀 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