with an instance running locally
go to any user profile url (localhost:8000/anyuser)
it will bring up this page...

can't read the buttons/search

Version

2.6.10

Reproduction link

https://github.com/vuejs/vue

Steps to reproduce

1. compare the AsyncComponentFactory definition with the document

What is expected?

attribute 'componen

I'd like to have a button that forces a re-render of the selected component when clicked. For example, adding a button like this on the right of the component controls:

This can be accomplished today by adding a new prop and changing the prop, but it's more work than I want to do.

What Happens

Oddly, Google, in my area, still indexes 4.0 version of the docs while the current version is 4.3. So the search redirects to https://getbootstrap.com/docs/4.0.

When I open up the docs from the search, naturally it says:

There's a newer version of Bootstrap 4!

When I click on that, it redirects to home page rather than the same page of the component.

What I Exp

Consider the following snippet run in the main process where one wants to listen for "will-prevent-default" events and after some asynchronous operation (do_something, a call which returns a Promise) initiated by the event listener, depending on the result (result) of the operation, call preventDefault on the even

The deprecated decodeDracoFile method should be removed and replaced with a parse method similar to other loaders. Currently decodeDracoFile does not propagate errors, and should do so. So probably a signature like:

dracoLoader.parse( arrayBuffer, /* options, maybe? */, onLoad, onError );

📚 Docs or angular.io bug report

Description

With CLI we're able to configure a certain preprocessor

Do you want to request a feature or report a bug? Feature

Summary 💡

https://github.com/mui-org/material-ui/blob/master/docs/src/pages.js#L19-L123 uses sometimes singular sometimes plural for the name of items:

Selects vs Progress for example. Use singular name everywhere.

Also add Dropdown alias for Select item. Like "Select (Dropdown)" or "Select / Dropdown"
![image](https://user-images.githubusercontent.com/19698636/65916668-08b38500-e3d6-

So getAllowedLocations is mentioned in the Atom flight manual, but it's not mentioned elsewhere in the docs. I thought I could implement just getDefaultLocation without having to also implement getAllowedLocations, but I get the following in the developer tools:

`C:\Use

Description

So our function arrayToHtmlList is in a pretty bad space and could use an update. We already had some discussion over at #675 but I wanted to move the update discussion over to an issue for more visibility.

Current problem:

It uses an awkward query selector instead of the `document.prototype.getElementBy

If you follow the readme procedure, the following error will occur in the first npm install express.

saveError ENOENT: no such file or directory, open '/xxx/xxx/package.json'

As you know, the cause is package.json does not exist.
Other users seem to have a similar error, so it seems better to add npm init to the readme.
Or I thought it would be nice to bring a link `Please follow

Documentation Is:

• Missing or needed
• Confusing
• Not Sure?

Global datasets options for existsing custom chart extension

There is a new structure to configure the datasets options at global level for each chart type.

In the [do

Hi, this is a feature request I suppose. The zip file download from the home page is a bit of a 'zip bomb'. I think it would be better to unzip into a contained folder as this can be quite annoying.

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

Existing Component

是

Component Name

site

Description

add TOC quick access.

example:
antd
![image](https://user-images.githubusercontent.com/8358236/482508

Do you want to request a feature or report a bug?
feature request

What is the current behavior?
Currently yarn why won't indicate any package info in the resolutions field

If the current behavior is a bug, please provide the steps to reproduce.

1. install a package with any version, e.g "pkg": "^1.0.0"
2. add resolutions field in package.json, pkg: "1.0.0"
3. upd

It will be nice to have a document guide to migrate from v0.100.2 to v1.0. Else if it's already there can it be displayed in a more prominent place in the landing page. I had a lot of struggle in migrating my things.