to reproduce:

1. go to localhost:8000/donate locally
2. click on show other ways to donate.
3. decrease the screen size below 400px

Interaction names longer than about 30 characters are truncated without tooltips and so cannot be seen. If you go to the "Interactions" tab of the profiler, both the left-hand column and the right-hand sidebar are of fixed size and show a truncated name.

This is a good first PR!

We should add some tests to cover #7036. They should cover both JavaScript and TypeScript support.

They can probably be added to test/fixtures.

• I have searched the issues of this repository and believe that this is not a duplicate.

What problem does this feature solve?

We have a case like this: after the onChange event emit, we will validate the targetKeys , if the validation has error, we hope there will be a red border at the outside of the targetKeys list, and the e

Select component's onChange is work, but it cannot render selected value.

import React, { useState } from 'react';
import InputLabel from '@material-ui/core/InputLabel';
import Select from '@material-ui/core/Select';
import MenuItem from '@material-ui/core/MenuItem';

export default function Test() {
  const [test, setTest] = useState({
    a: '',
    b: '',
    sum: {

https://github.com/storybookjs/presets/blob/master/packages/preset-storysource/index.js

• Move the preset from the presets repo into this package
• Update it to use source-loader
• Update docs

Bug report

Describe the bug

Default viewport tag is being appended to and not replaced whenever you use define your own custom viewport tag.

To Reproduce

Define a simple _app.tsx that attempts to set a custom viewport meta tag.

import App from 'next/app'
import Head from 'next/head'

class MyApp extends App {
  render() {
    const { Component, pageProp

Renovate is fantastic but because of our config at the moment, we get several updates in a day.

We should probably do two things

• batch all minor updates in a single PR
• schedule them at a reasonable time (twice a week, perhaps at 10 am GMT)

This should go in config at https://github.com/gatsbyjs/gatsby/blob/master/renovate.json

Documentation for options is at https://docs.renovat

• I am on the latest Hyper.app version
• I have searched the issues of this repo and believe that this is not a duplicate

❌ to the ☕ script! ES6 is cleaner, more modern, and has a much more reliable linter—plus, people know how to read it—so we want to convert everything in the codebase. Most of the code is already there, but there are still specs written in Coffee.

Just like we have a create-react-app for react, we now have nano-preact-app for preact.

There's not much bloatware. Just an index file that renders our App, an App component that showcases how we can create a Component and a couple of build scripts for developers.

I am also using Parcel to build the project.

PRs and issues welcome. Hope it helps everyone!

Here it is: [nano-preact-a

问题描述
创建FunctionComponent类型的页面，设置页面的config时不方便，希望在官方的FunctionComponent中加入config的类型定义

复现步骤

现在通过新建的taroPatch.d.ts实现的

import Taro from '@tarojs/taro'

declare module '@tarojs/taro' {
  interface FunctionComponent {
    config?: Taro.Config
  }
}

期望行为
直接在node_modules\@tarojs\taro\types\index.d.ts中加入config类型定义

报错信息

![image](https://user-images.gith

修改了 config\config.js 的 proxy 的内容,浏览器这边还是走的8000
proxy: { '/api': { target: 'http://localhost:8888/', changeOrigin: true, }, },

@cloverich We shall also figure out to deal with that README, I did not like that I had to do the change (#2144) twice, even though it was a small thing.

If we were about to copy those files, how do we ensure people will edit the right one?

Is it really that problematic with Docusaurus to reference the one from the root folder? Some sort of aliasing?

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

📖 Documentation

Both, formik and material-ui are two very prominent libraries.
https://github.com/stackworx/formik-material-ui is a binding to ease the use of formik with material-ui and I think it's worth mentioning this in the docs.

The current React-Redux docs aren't very helpful, for a lot of reasons:

• They're just a Markdown file in the repo, instead of being published in HTML form
• It feels very "dense" and jargon-heavy
• It doesn't clearly lay out the various options for connect and ways that you can use it
• It's primarily in API reference form, rather than a "how to"

We do also have the "Using React with R