问题描述

Input,TextArea组件文档没有介绍小程序端的兼容状况

复现步骤

亲爱的开发者们您好，我遇到的问题如下

1. 我想要使用Input,Textarea等组件，并想要运用于小程序中
2. 查阅taro中该组件相关的文档后，没有只有H5/RN端介绍了兼容性差异，而微信，支付宝等小程序端没有介绍兼容情况，如下图所示

3.请问能够补充一下吗
4. 非常感谢！

期望行为

能够在Input,Textarea文

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

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

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

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

Description

Bit know to parse javascript, React and Vue component documentation, but not do it for Angular component.

Specifications

• Bit version: 14.4.3
• Node version: 12.7.0

Context and additional information

Angular button component for example:
https://bit.dev/primefaces/primeng/button

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.

Not sure why but document.body is null or undefined

const getjQuery = () => {
const { jQuery } = window
if (jQuery && !document.body.hasAttribute('data-no-jquery')) {
return jQuery
}
return null
}

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?

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-

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

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?

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.

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.

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

https://emotion.sh/

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

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