Simon Siefke

Results 12 comments of Simon Siefke

I believe this would be a great addition to the docs! Having used puppeteer before, most of my code intuitively looked like this: ```js // delete file await page.click('text=file1.txt', {...

@tonivj5 Do you have an example where it doesn't work? The code snippet in this issue its definitely working for me with multi-cursor. ![it-works](https://user-images.githubusercontent.com/23744935/80373288-2033ed00-8895-11ea-9387-9dace2186e33.gif)

Great catch! Will try to improve on that.

First: Download the project and install dependencies ```sh git clone [email protected]:formulahendry/vscode-auto-rename-tag.git && cd vscode-auto-rename-tag && npm ci ``` Then click on the debug icon in VSCode and then "Start Debugging"...

![diff](https://user-images.githubusercontent.com/23744935/82748212-8a5e8580-9da0-11ea-9947-4b47785274bb.png) It looks like v0.1.3 doesn't include the fix for https://github.com/formulahendry/vscode-auto-rename-tag/issues/535 @formulahendry I think you might have forgotten to run `npm run package` before publishing v0.1.3

I've uninstalled and the reinstalled the extension and now it works. It's probably an issue with the VSCode Marketplace then because the code in `~/.vscode/extensions/formulahendry.auto-rename-tag-0.1.3` is different now (and includes...

@jordyvandomselaar There is an [issue with the VSCode marketplace](https://github.com/microsoft/vscode/issues/98472) which causes VSCode to install a wrong version. You can download v0.1.4 manually: Step 1: Download [auto-rename-tag-0.1.4.zip](https://github.com/formulahendry/vscode-auto-rename-tag/files/4872248/auto-rename-tag-0.1.4.zip) and extract the zip...

To provide some more context, here is a simple example where it works: ```jsx const Button = () => click me ``` Here is a simple example where it doesn't...

I think this might be the best place. Vue router is already validating the type of the component [here](https://github.com/vuejs/vue-router/blob/dev/src/create-route-map.js#L68). If the error message would come from Vue router instead of...

Maybe the `CSSStyleSheet` api could useful for this, for example: ```js const sheet = new CSSStyleSheet(); sheet.replaceSync("a { color: red; }"); document.adoptedStyleSheets.push(sheet) ```