profile
viewpoint
Artur Tagisow 3nuc Białystok, Poland tagisow.dev Front-end developer

3nuc/biometria-ps-keystroke-dynamics 0

Drugie zadanie projektowe składa się z następujących elementów: Realizacja pełnoprawnego systemu biometrycznego opartego o szybkość pisania na klawiaturze. W jego skład wchodzą dwa moduły: moduł pobierania danych oraz moduł klasyfikacji z wykorzystaniem algorytmu k-NN. [0,5 pkt] Liczność bazy danych - aby uzyskać pełne 0,5 punktu należy posiadać przynajmniej 10 użytkowników, opisanych każdy przez co najmniej 3 próbki. [1 pkt] Poprawność realizacji modułu zbierania próbek i zapisu wektorów cech do bazy danych (średni czas wciśnięcia przycisku dla każdej z liter + klasa obiektu). [1,5 pkt] Badanie jakości systemu z wykorzystaniem metody k-NN oraz metryk: Euklidesa, Manhattan oraz Czebyszewa. [1 pkt] Jakość przygotowanego sprawozdania i wniosków. Przewiduje się dodatkowe punkty za zaimplementowanie dwóch dodatkowych metryk: Bray Curtisa oraz Mahalanobisa. Wynikiem Państwa pracy musi być sprawozdanie w którym opiszą Państwo pokrótce przygotowany system (sposób pobierania próbek), zamieszczą wykresy dotyczące jakości systemu (przy różnej liczbie k) oraz zaprezentują wnioski z wykonanych eksperymentów.

3nuc/blog 0

projekt rswta http://cez.wi.pb.edu.pl/moodle/file.php/170/ps/projekty.pdf (7. blog)

3nuc/cron 0

projekt systemy operacyjne

3nuc/docs-next 0

Vue 3 core documentation

issue commentramda/ramda

Error when using Ramda with Jest

https://stackoverflow.com/a/59880149/10706046 fixed this for me. I'm working on a ts project and sometimes it uses old .js files so I needed to take the .js file extension in Jest into account.

//package.json > "jest" property
    "transform": {
      "^.+\\.vue$": "vue-jest",
      "\\.ts$": "ts-jest",
      "^.+\\.tsx?$": "ts-jest",
+     "\\.js$": "babel-jest",
      ".+\\.(css|styl|less|sass|scss|svg|png|jpg|ttf|woff|woff2)$": "jest-transform-stub"
    },
thebedivere

comment created time in 2 days

Pull request review commenttypescript-cheatsheets/vue

Docs Reshuffle [WIP]

+# Class Components++## Overview++[Vue Class Components](https://class-component.vuejs.org/) offers an alternative class-style syntax for Vue components which integrates well with TypeScript.++To have consistent support for decorators in your Vue components, it's also recommended to install [vue-property-decorator](https://github.com/kaorun343/vue-property-decorator).+++To get started with both libraries in your existing Vue project, run: +```+npm install vue-class-component vue-property-decorator+```++You only need to import `vue-property-decorator` into your `.vue` file as it extends `vue-class-component`. ++You can now write TS in your components like this:++```vue+<template>+  <div>+    {{ count }}+    <button v-on:click="increment">+</button>+    <button v-on:click="decrement">-</button>+    {{ computedValue }}+  </div>+</template>++<script lang="ts">+import { Vue, Component } from "vue-property-decorator";++@Component+export default class Hello extends Vue {++  count: number = 0+  vue: string = "vue"+  ts: string = "ts"++  // Lifecycle methods can be accessed like this+  mounted() {+    console.log('component mounted')+  }++  // Method are component methods+  increment(): void {+    this.count+++  }++  decrement(): void {+    this.count--+  }++  // Computed values are getters+  get computedValue(): string {

Yes that's what I mean - in my experience classes don't have this caveat. Not sure if there's a source that confirms this definitely but I've never ran into this with classes

chiubaca

comment created time in 5 days

PullRequestReviewEvent

Pull request review commenttypescript-cheatsheets/vue

Docs Reshuffle [WIP]

+# Class Components++## Overview++[Vue Class Components](https://class-component.vuejs.org/) offers an alternative class-style syntax for Vue components which integrates well with TypeScript.++To have consistent support for decorators in your Vue components, it's also recommended to install [vue-property-decorator](https://github.com/kaorun343/vue-property-decorator).+++To get started with both libraries in your existing Vue project, run: +```+npm install vue-class-component vue-property-decorator+```++You only need to import `vue-property-decorator` into your `.vue` file as it extends `vue-class-component`. ++You can now write TS in your components like this:++```vue+<template>+  <div>+    {{ count }}+    <button v-on:click="increment">+</button>+    <button v-on:click="decrement">-</button>+    {{ computedValue }}+  </div>+</template>++<script lang="ts">+import { Vue, Component } from "vue-property-decorator";++@Component+export default class Hello extends Vue {++  count: number = 0+  vue: string = "vue"+  ts: string = "ts"++  // Lifecycle methods can be accessed like this+  mounted() {+    console.log('component mounted')+  }++  // Method are component methods+  increment(): void {+    this.count+++  }++  decrement(): void {+    this.count--+  }++  // Computed values are getters+  get computedValue(): string {+    return `${vue} and ${ts} rocks!`+  }+}+</script>+```+See the [full guide for Vue Class Components](https://class-component.vuejs.org/guide/class-component.html#data).++> _Class components should not confused with the now abandoned [Class API proposal](https://github.com/vuejs/rfcs/pull/17#issuecomment-494242121)._++## Props+You can use the `Prop` decorator to annoate your prop types like so:++```ts+<script lang="ts">+import { Vue, Component, Prop } from "vue-property-decorator";++interface PersonInfo { +  firstName: string,+  surname: string,+  age: number+}++@Component+export default class InfoCard extends Vue {+  @Prop({ required: true }) readonly info: PersonInfo;

I meant ”readonly propName[? or ! missing here]: SomeType". Don't you get a TS error if you write just
"readonly propName: SomeType" instead of "readonly propName!: SomeType"?

chiubaca

comment created time in 5 days

PullRequestReviewEvent

issue commentfirefox-devtools/vscode-firefox-debug

Extensions disabled

You need to explicitly set the profile you want Firefox to use while debugging. Otherwise I think it creates an empty profile.

  1. Go to about:profiles (type this in URL bar) in Firefox and there you'll see "This is the profile in use and it cannot be deleted".
  2. Look at the end of the path to the profile. There you'll see something like 86jtnway.default-nightly. Remember the part after the dot (default-nightly).
  3. Add profile: [value after the dot] to your launch config (profile: 'default-nightly'). You may not have a default-nighlty profile, you'll have only default if you use the stable Firefox etc. You can also create a new profile in about:profiles that you use in debugging (which is what I did and called it 'vscode-debug').

Though keep in mind if you use the same profile for browsing while having a debugging session open you'll have problems with freezing (if you try going to a page in your browsing window it'll be loading forever).

I recommend creating a fresh profile (eg. vscode-debug), installing only the extensions you need in it, then running debugging on that profile. If you do that, you'll also need to run your debug firefox with no-remote to force it to start a new Firefox instance, rather than connect to your browsing one.

See my launch config below. It has some options that I've forgotten what they do at this point :P

The problem with this solution is that whenever

From github readme:

  • profileDir, profile: You can specify a Firefox profile directory or the name of a profile created with the Firefox profile manager. The extension will create a copy of this profile in the system's temporary directory and modify the settings in this copy to allow remote debugging. You can also override these properties in your settings (see below). The default profile names used by Firefox are default, dev-edition-default and default-nightly for the stable, developer and nightly editions, respectively.

Here's my launch configuration:

      {
        "name": "Firefox attach (local!)",
        "type": "firefox",
        "firefoxExecutable": "C:\\Program Files\\Firefox Nightly\\firefox.exe",
        //no-remote allows running two different profiles at the same time
        //without this, firefox will freeze if you have a debug instance and personal web browsing instance open
        "firefoxArgs": ["-no-remote"],
        "profile": "vscode-debug",
        //without this, the extensions in the above profile disappear (vue devtools etc.) even though I explicitly installed them and want to keep them
        "keepProfileChanges": true,
        "request": "launch",
        "reAttach": true,
        "url": "https://localhost:4402",
        "webRoot": "${workspaceFolder}"
      },
Yajo

comment created time in 9 days

pull request commenttypescript-cheatsheets/vue

Docs Reshuffle [WIP]

Hey I know I came out of nowhere but I left some of my thoughts, hope it's ok

chiubaca

comment created time in 9 days

PullRequestReviewEvent

Pull request review commenttypescript-cheatsheets/vue

Docs Reshuffle [WIP]

+# Class Components++## Overview++[Vue Class Components](https://class-component.vuejs.org/) offers an alternative class-style syntax for Vue components which integrates well with TypeScript.++To have consistent support for decorators in your Vue components, it's also recommended to install [vue-property-decorator](https://github.com/kaorun343/vue-property-decorator).+++To get started with both libraries in your existing Vue project, run: +```+npm install vue-class-component vue-property-decorator+```++You only need to import `vue-property-decorator` into your `.vue` file as it extends `vue-class-component`. ++You can now write TS in your components like this:++```vue+<template>+  <div>+    {{ count }}+    <button v-on:click="increment">+</button>+    <button v-on:click="decrement">-</button>+    {{ computedValue }}+  </div>+</template>++<script lang="ts">+import { Vue, Component } from "vue-property-decorator";++@Component+export default class Hello extends Vue {++  count: number = 0+  vue: string = "vue"+  ts: string = "ts"++  // Lifecycle methods can be accessed like this+  mounted() {+    console.log('component mounted')+  }++  // Method are component methods+  increment(): void {+    this.count+++  }++  decrement(): void {+    this.count--+  }++  // Computed values are getters+  get computedValue(): string {

Worth mentioning vue-property-decorator doesn't have the same caveat as https://github.com/typescript-cheatsheets/vue/pull/10/files#diff-04c6e90faac2675aa89e2176d2eec7d8R180 (ie. computeds are normally inferred)

chiubaca

comment created time in 9 days

Pull request review commenttypescript-cheatsheets/vue

Docs Reshuffle [WIP]

+# Class Components++## Overview++[Vue Class Components](https://class-component.vuejs.org/) offers an alternative class-style syntax for Vue components which integrates well with TypeScript.++To have consistent support for decorators in your Vue components, it's also recommended to install [vue-property-decorator](https://github.com/kaorun343/vue-property-decorator).+++To get started with both libraries in your existing Vue project, run: +```+npm install vue-class-component vue-property-decorator+```++You only need to import `vue-property-decorator` into your `.vue` file as it extends `vue-class-component`. ++You can now write TS in your components like this:++```vue+<template>+  <div>+    {{ count }}+    <button v-on:click="increment">+</button>+    <button v-on:click="decrement">-</button>+    {{ computedValue }}+  </div>+</template>++<script lang="ts">+import { Vue, Component } from "vue-property-decorator";++@Component+export default class Hello extends Vue {++  count: number = 0+  vue: string = "vue"+  ts: string = "ts"++  // Lifecycle methods can be accessed like this+  mounted() {+    console.log('component mounted')+  }++  // Method are component methods+  increment(): void {+    this.count+++  }++  decrement(): void {+    this.count--+  }++  // Computed values are getters+  get computedValue(): string {+    return `${vue} and ${ts} rocks!`+  }+}+</script>+```+See the [full guide for Vue Class Components](https://class-component.vuejs.org/guide/class-component.html#data).++> _Class components should not confused with the now abandoned [Class API proposal](https://github.com/vuejs/rfcs/pull/17#issuecomment-494242121)._++## Props+You can use the `Prop` decorator to annoate your prop types like so:++```ts+<script lang="ts">+import { Vue, Component, Prop } from "vue-property-decorator";++interface PersonInfo { +  firstName: string,+  surname: string,+  age: number+}++@Component+export default class InfoCard extends Vue {+  @Prop({ required: true }) readonly info: PersonInfo;

Don't vue-property-decorator props definitions need to have ! after the name? > readonly info!: PersonInfo.

Consider @Prop({required: true, type: Object}) to be explicit that types are not inferred from ts type (though it's possible if you use reflect-metadata)

chiubaca

comment created time in 9 days

PullRequestReviewEvent

issue commentstorybookjs/storybook

Vue with css modules

I created a repro case here (:class="$style.myClass" in IDE turning into class="" in browser element inspector): https://github.com/3nuc/storybook-is9297 if someone wants to dig in for docs purposes

@shilman I didn't really track down the issue, I just changed the versions blindly and it started working :P Would be nice to know what is missing in the Webpack dist that caused :class="[$style.myStyle]" to turn into class="" in the inspector in Storybook though.

As for the docs:

  1. Removing the instructions to download css-loader sass-loader style-loader is slightly "less bad". This reduces the probability of someone running into this issue, but someone that has css-loader and style-loader with too new versions explicitly in their package.json will still run into this issue. I know maintaining loaders is a nightmare as they change property names every so often
  2. Seeing how all config examples in this issue use the oneOf rule to allow using both <style> and <style module>, setting up Storybook for a project that uses css modules and vanilla css interchangeably may be a common usecase. I noticed there's an undocumented options.rule option in preset-scss: https://github.com/storybookjs/presets/blob/0ad1358dbdb515a0f6c1c78fa65c375ea1f8f87c/packages/preset-scss/index.js#L20 . It may be worth adding to the docs that you can put the oneOf rule there and pasting one of our webpack configs
  3. Adding a section about how to troubleshoot class="" - I don't know Webpack enough to understand where to look in the dist to understand why this is happening, so I can't write anything meaningful. Things I've tried:
    • Comparing webpack configs side by side vue inspect > vue-webpack-config.log and npx start-storybook --loglevel silly --debug-webpack > storybook-webpack-config.log (You can also do that in my repro case repo). In 'storybook-webpack.config.log' in the 'preview webpack config' section you can see that it storybook for it's own css module.rules uses this:
      {
        test: /\.css$/,
        sideEffects: true,
        use: [
          '/home/artur/dev/storybook-is9297/node_modules/@storybook/core/node_modules/style-loader/dist/cjs.js',
          {
            loader: '/home/artur/dev/storybook-is9297/node_modules/@storybook/core/node_modules/css-loader/dist/cjs.js',
            options: { importLoaders: 1 }
          },

but the rule added by us at the end uses

      {
        test: /\.scss$/,
        oneOf: [
          {
            resourceQuery: /module/,
            use: [
              'vue-style-loader',
              {
                loader: 'css-loader', //not absolute path, so uses root css-loader in package.json
                options: { modules: { localIdentName: '[name]-[hash]' } }
              },
              'sass-loader'
            ]
          },
          { use: [ 'vue-style-loader', 'css-loader', 'sass-loader' ] }
        ]
      }
chrisjbrown

comment created time in 9 days

push event3nuc/storybook-is9297

Artur Tagisow

commit sha 188997cf8ddd1322bdfe36b1bcd9dcf582981cf4

make class='' show up in inspector in storybook on App component

view details

push time in 9 days

push event3nuc/storybook-is9297

Artur Tagisow

commit sha 2177dfed1bf4e268a935598ef7f25538d137e00a

update readme.md

view details

push time in 9 days

create barnch3nuc/storybook-is9297

branch : master

created branch time in 9 days

created repository3nuc/storybook-is9297

created time in 9 days

issue commentstorybookjs/storybook

Vue with css modules

The above config wasn't working for me initially, because I followed the advice from https://github.com/storybookjs/presets/tree/master/packages/preset-scss#basic-usage saying to do yarn add -D @storybook/preset-scss css-loader sass-loader style-loader. I didn't have css-loader and style-loader in my package.json, so I was relying on the package versions installed by subdependencies.

After running the mentioned yarn add, it installed style-loader@2.0.0, css-loader@4.3.0 whereas storybook uses style-loader@1.3.0, css-loader@3.6.0 internally.

To fix the issue, I just changed the style-loader and css-loader to 1.3.0 and 3.6.0 respectively

chrisjbrown

comment created time in 10 days

startedstorybookjs/storybook

started time in 10 days

issue commentvuejs/vetur

Sass intellisense

Webstorm supports cross-file variable extraction, go to definition etc., so should be possible 2 years later image

marioffdsw

comment created time in 18 days

issue commentprettier/eslint-config-prettier

Bug (?) : prettier and eslint rules indent conflicting on interpolated strings

If anyone has the same problem: This plugin disables rules in eslint and makes prettier take over (as lydell said above) If you have something set in .eslintrc.js in the "rules" property, it cannot be overwritten by this plugin.

For me, in vscode I had these lines:

    disabledWhen(
      ({ something }) =>
        something.condition ||
        something.condition1 <---- 'eslint(comma-dangle) Missing trailing semicolon)
    ),

and when I added the semicolon, the eslint(comma-dangle) warning turned into a eslint(prettier/prettier) warning saying "Remove trailing comma" or something like that. So it was an endless loop - I have autofix on save so when I pressed CTRL+S the warnings would toggle between comma-dangle and prettier/prettier

For me, it was the comma-dangle rule in eslint in the "rules" section. I just removed it from .eslintrc.js and added the (almost) equivalent trailingCommas: 'all' in .prettierrc

StephanePiresPro

comment created time in 18 days

startedmicrosoft/winget-cli

started time in 19 days

issue openedreminder-bot/bot

Allow escaping @mention when setting reminder

Consider this: You want the bot to call ping a group of people (eg. @everyone) at your specified date.

Writing $natural in 30 minutes send @everyone time is up!! will work - the users will be notified. But they will also be noitified when you set the reminder.

Would it be possible to do something like $natural in 30 minutes send \@\everyone hi! (so everyone won't be pinged when setting the reminder). But after 30 minutes the bot will send @everyone and everyone will be pinged.

created time in 19 days

startedunivrsal/input-overlay

started time in 20 days

startedvuejs/component-compiler-utils

started time in 20 days

startedeslint/eslint

started time in 21 days

push event3nuc/demo-vue-eslint-force-dot-vue-extension-in-imports

Artur Tagisow

commit sha efa5f82fe306e97a1c979e9c1049dbfb2409af57

Update README.md

view details

push time in 21 days

push event3nuc/demo-vue-eslint-force-dot-vue-extension-in-imports

Artur Tagisow

commit sha 47088bc587650d7210a7a702b36a6fa7309ded2c

Update README.md

view details

push time in 21 days

push event3nuc/demo-vue-eslint-force-dot-vue-extension-in-imports

Artur Tagisow

commit sha fa648520b8c5ad4ab24feeffd79b81b15d2916de

Update README.md

view details

push time in 21 days

push event3nuc/demo-vue-eslint-force-dot-vue-extension-in-imports

Artur Tagisow

commit sha 70cdb2dca06ed6a157323f1b85e7b1fa449aa8ce

Update README.md

view details

push time in 21 days

issue comment3nuc/demo-vue-eslint-force-dot-vue-extension-in-imports

A few issues

The fix for this was released in https://github.com/benmosher/eslint-plugin-import/releases/tag/v2.22.1

I updated the repo.

To anyone who has the same issue in the future: please run:

  • npm list eslint-plugin-import and make sure the version of eslint-plugin-import is >= 2.22.1
wenfangdu

comment created time in 21 days

push event3nuc/demo-vue-eslint-force-dot-vue-extension-in-imports

Artur Tagisow

commit sha cc702091ef04b1863305eefe3090776ae2622e1c

Update to eslint-plugin-import 22.1.0 This fixes an issue where eslint-plugin import would not care if files in src folder had an extension So eg. import component from @/ComponentInSrc would not cause eslint to throw an error, even though eslint config indicates it should This was happening because @/anythinghere was treated like a scoped module before eslint-import-plugin 22.1.0 (eg. @vue/cli => import something from '@vue/cli' <-- no sane person requires an extension when importing from a node_module)

view details

Artur Tagisow

commit sha 638b186a2b9b7b5eed54a64481354e09fc978f5c

Merge branch 'master' of https://github.com/3nuc/demo-vue-eslint-force-dot-vue-extension-in-imports

view details

push time in 21 days

push event3nuc/demo-vue-eslint-force-dot-vue-extension-in-imports

Artur Tagisow

commit sha 97f313c46bfda165801152e3d37aec7043c04e29

Update README.md

view details

push time in 21 days

startedmicrosoft/terminal

started time in 22 days

issue commentvuejs/vetur

Have Auto Close / Rename Tag for html section

microsoft/language-server-protocol#1092 👀

octref

comment created time in 23 days

push event3nuc/vuekcal

Artur Tagisow

commit sha 6c56bca3db083af8fe4a673a0203969084eeaaff

Merge branch 'master' of github.com:3nuc/vuekcal

view details

push time in 24 days

push event3nuc/vuekcal

Artur Tagisow

commit sha 06df386553193c69346770d28e6ab20c8b04a25c

dir structure

view details

Artur Tagisow

commit sha 30bf6990fce5e790d0d506f87b01af9fa2273b47

Merge branch 'master' of github.com:3nuc/vuekcal

view details

push time in 24 days

push event3nuc/vuekcal

Artur Tagisow

commit sha 5d9cc791f7c9d04257505579ce5caec14cc2901d

Update main.yml

view details

push time in 24 days

push event3nuc/vuekcal

Artur Tagisow

commit sha 62da0f761050a2ef472fb93f261e2e92b3a84b70

Create main.yml

view details

push time in 24 days

create barnch3nuc/vuekcal

branch : master

created branch time in 24 days

created repository3nuc/vuekcal

created time in 24 days

issue openedBaizey/UniversalAutomaticCurrencyConverter

Add setting for turning off logging to console

image I understand they're for easier debugging since someone can just copy-paste the output, but in the end it's annoying if you're a frontend dev that constantly sees this in console.

Sure it's possible to filter this out in FF using -uacc but it's not persistent

created time in 24 days

startedintlify/vue-i18n-next

started time in 24 days

startedjoaojosefilho/IdentityServer4AndApi

started time in 24 days

startedjoaojosefilho/vuejsOidcClient

started time in 24 days

issue commentposva/pinia

Permit to specify the State structure when using createStore

Weird. The same but with object method syntax does not have type safety even when just inferring (no interface):

import { createStore } from 'pinia';

export const userStore = createStore({
  id: 'userStore',
  state() {
    return {
      name: 'Pinia'
    };
  },
  getters: {
    // @ts-expect-error ts2339 (no error thrown)
    nameCapitalized: (state, getters) => state.somethingThatDoesntExist.toUpperCase()
  }
})
edimitchel

comment created time in 24 days

created repository3nuc/vscode-firefox-debug-is228

created time in 24 days

issue openedfirefox-devtools/vscode-firefox-debug

Path Mapping Wizard shows success message after failing to add pathMapping to launch.json which is invalid JSON

Repro

  1. Create a launch.json which is not valid json (example - see lack of comma at line 20)
  2. Set a breakpoint in a file that will trigger Path Mapping Wizard notification that suggests adding a new pathMapping automatically
  3. Click button in notification so Path Mapping Wizard attempts to add a new pathMapping entry to launch.json

vscode 1.50.0-insider in WSL2 Ubuntu 18.04, vscode-firefox-debug 2.9.1

What happens after repro

launch.json stays the same, no path is added to the invalid json, but the succes notification "path mapping added, restart your debug session" appears

What should happen after repro

launch.json stays the same, but an error notification should be shown saying "can't add pathMapping to launch.json which is not valid JSON. Check the Problems tab while viewing launch.json for details"

created time in 24 days

issue commentpython-kasa/python-kasa

Install on Ubuntu 18.04 no luck

Had to update to python 3.8 from python 3.6 in order for this to go away.

Just follow this guide: https://gist.github.com/plembo/6bc141a150cff0369574ce0b0a92f5e7

mdetweiler

comment created time in 25 days

issue commentIdentityModel/oidc-client-js

Use unminified sources as "main"

Had to do what OP did today. This user did too: https://github.com/IdentityModel/oidc-client-js/issues/1044#issuecomment-591625560

This is quick to fix yourself when you know where to look, but otherwise it's another hurdle you need to jump over to debug your app.

Alxandr

comment created time in 25 days

startedfirefox-devtools/vscode-firefox-debug

started time in 25 days

issue commentvuejs/vetur

Shims not working for Vue 3 + TypeScript

Shouldn't you just do export default string?

dannysmc95

comment created time in a month

issue commentvuejs/vue-test-utils

How to use typescript correctly?

@vegerot

  1. Why doesn't Wrapper<YourComponentHere> come with all the types needed?

From what I know, it's difficult to extract this information from an SFC .vue file. @ znck is doing God's work regarding this in typescript-plugin-vue, though it's currently experimental

I assume this is why all .vue imports are cast by TS to the generic Vue interface which doesn't contain prop names etc. If you want to know where this is done in your project, look for the shims-vue.d.ts file in your /src folder. You'll find the below snippet there:

declare module '*.vue' { //for every .vue file
  import Vue from 'vue';
  export default Vue; //assume it's default import is of type Vue (generic interface without type information)
}
  1. Given 1, what's the difference between Wrapper<YourComponentHere & { [key: string]: any }> and Wrapper<Vue & { [key: string]: any }>?

There's no difference. Both YourComponentHere and Vue are of type Vue. I wrote YourComponentHere because I guess it's more future-proof (if there's an ability to get .ts information from a .vue file, you wouldn't want your project to use Vue iface everywhere in your tests). And since you already have to import the component to shallowMount it, why not?

kimond

comment created time in a month

startedclapfoot/warapi

started time in a month

issue openedolegwukr/polish-privacy-filters

money.pl

Np. na https://www.money.pl/gospodarka/wiadomosci/artykul/zwrot-pieniedzy-konto-platnosc-karta-bank,188,0,2422972.html image

money.pl przewinęło się w #87

created time in 2 months

push event3nuc/vue-test-utils

Artur Tagisow

commit sha b8a178a4acaba7bcafe58070f8f16718cbc7a373

Change bold text to header so it can be linked to Setting the event target is a pretty important caveat to the point where someone may want to include a "[vue-test-utils-url/trigger#setting-the-event-target" url in comment code

view details

push time in 2 months

fork 3nuc/vue-test-utils

🔬 Utilities for testing Vue components

https://vue-test-utils.vuejs.org

fork in 2 months

push event3nuc/vetur

Artur Tagisow

commit sha 60cfda0942475def09e16f00f21caac875fb5a8f

Add showing #slot attrs in symbols fixes #2169

view details

Artur Tagisow

commit sha a130dcd8dd1ace970c24e72e390c06da7794fdeb

Add unit tests

view details

Artur Tagisow

commit sha 05b922cb11f345b0bdd5c7794592eac901972626

Merge branch 'show-slots-in-symbols' of https://github.com/3nuc/vetur into show-slots-in-symbols

view details

push time in 2 months

issue commentvuejs/vetur

Intellisense in latest Vetur is painfully slow

The difference between editing a .ts file and .vue lang="ts" file in the same workspace is very noticeable. IntelliSense in .ts is much faster, though I use the TS nightly extension. Not sure if others share the same experience

kjeksfjes

comment created time in 2 months

startedmicrosoft/team-explorer-everywhere

started time in 2 months

PR opened vuejs/vetur

Add showing #slot attrs in symbols

fixes #2169

<!-- Please follow https://github.com/vuejs/vetur/wiki/Pull-Request-Guidance -->

+17 -0

0 comment

2 changed files

pr created time in 2 months

push event3nuc/vetur

Artur Tagisow

commit sha 60cfda0942475def09e16f00f21caac875fb5a8f

Add showing #slot attrs in symbols fixes #2169

view details

push time in 2 months

push event3nuc/vetur

Artur Tagisow

commit sha d55198bb6b7b7fcb681c2444f1f971dd07266ed6

Add showing #slot attrs in symbols

view details

push time in 2 months

issue openedvuejs/vetur

Implement more detailed symbol info for tags with slot-related attributes

<!-- Check those before opening an issue -->

  • [x] I have searched through existing issues

Feature Request

<!-- Please only describe one feature request in one single issue. -->

  1. Show slots in vscode symbol browser: obraz

  2. Show slot[name="slotname"] in symbol search instead of just slot in symbol search

Things I'm not sure about:

  • Should old slot & slot-scope syntax be supported?
  • Displaying the slot like div#id.class #slotname is weird as two attrs use the # symbol (which is normally reserved for id). Maybe div#id.class[#slotname] would be better? VSCode never returns attr info for symbols in .html files though (eg. <input type='number'> still returns symbol info like input rather than input[type='number']

created time in 2 months

push event3nuc/vetur

Artur Tagisow

commit sha 0d152d7b944ad94adb5a20013ded5c3316bbd90c

Add showing #slot attrs in symbols

view details

push time in 2 months

create barnch3nuc/vetur

branch : show-slots-in-symbols

created branch time in 2 months

startedShareX/ShareX

started time in 2 months

issue commentvuejs/vetur

Getting code actions from ''Vetur', 'Eslint'' takes too long!

Not sure if this is not another extension I have but just throwing it out there - does anybody's code sometimes get mangled (eg. one line gets duplicated) after Vetur + Eslint code actions finish after a long time?

daolanfler

comment created time in 2 months

startedtokyo-metropolitan-gov/covid19

started time in 2 months

issue commentvuejs/vetur

Intellisense in latest Vetur is painfully slow

Having similar issue but with TypeScript intellisense of instance properties in <script> or <template> tags.

What I did:

  1. Open https://github.com/tokyo-metropolitan-gov/covid19/blob/development/components/PositiveRateMixedChart.vue (in vscode after cloning repo and npm install, not on web)
  2. Go to <template>
  3. Write down v-text="displayOptionHeader." (notice dot at end) in some random tag
  4. Pressed start CPU profiling in Chrome
  5. Return to vscode after '.' and press ctrl+space
  6. Wait for intellisense box to appear with suggestions based on TS interface
  7. *Stop CPU profiling covid-19-ctrl-space-in-template.zip

I mainly experience it at work in a vue-property-decorator TS project but I don't wanna share the profile from there

kjeksfjes

comment created time in 2 months

startedtypescript-cheatsheets/vue-typescript-cheatsheet

started time in 2 months

push event3nuc/dotfiles

Artur Tagisow

commit sha 3dda435fa954d81945cbb9b7b0699224bda68272

Add nvm

view details

push time in 2 months

push event3nuc/dotfiles

Artur Tagisow

commit sha 1687b99dfe16e87e90c5e9e09465e0ddf644842b

Add nvm

view details

push time in 2 months

push event3nuc/dotfiles

Artur Tagisow

commit sha 91ff5cbc8c7cf0467c4085bb6886fd8053039957

Fix gitignore Fix gitignore

view details

Artur Tagisow

commit sha 5ec2d245c8e80eaf90c54c5895b955d1e017123e

Add vim-surround

view details

Artur Tagisow

commit sha eb2386f20d9d5f8e134003116659ceeb0caee096

Add nvm

view details

push time in 2 months

created repository3nuc/vuex-experiments

created time in 2 months

startedfirefox-devtools/ux

started time in 3 months

PR opened vuejs/vetur

Mention "attributes" in workspace tags docs
+5 -3

0 comment

1 changed file

pr created time in 3 months

push event3nuc/vetur

Artur Tagisow

commit sha cf57e15abe80891901f78e7afd578d577703f217

Mention adding attribute intellisense in docs

view details

push time in 3 months

push event3nuc/vetur

ktsn

commit sha 1766c21de68d0c7af3a3365aab37d13df26188b2

Move ts to language server kind utils

view details

ktsn

commit sha 2255bc51103a7bcbdf2da94896ade00e9c046adf

Fix invalid assertion in test case

view details

ktsn

commit sha 54581e882b981f3bbcc801395f483483aeaa863c

Use constant for component variable name in transformed code

view details

ktsn

commit sha 271dbfcd9b1be62f847e6edf0041ee0775ee2f91

Use typescript info for interpolation completion

view details

dependabot-preview[bot]

commit sha 659d4076b73856dfa54f5923f070525cbcd4e253

Bump prettier-eslint from 8.8.2 to 9.0.1 in /server Bumps [prettier-eslint](https://github.com/prettier/prettier-eslint) from 8.8.2 to 9.0.1. - [Release notes](https://github.com/prettier/prettier-eslint/releases) - [Changelog](https://github.com/prettier/prettier-eslint/blob/master/CHANGELOG.md) - [Commits](https://github.com/prettier/prettier-eslint/compare/v8.8.2...v9.0.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

dependabot-preview[bot]

commit sha 491010ba06bc49b34632d9e9a2e021613ac074f6

Bump lint-staged from 9.5.0 to 10.0.8 Bumps [lint-staged](https://github.com/okonet/lint-staged) from 9.5.0 to 10.0.8. - [Release notes](https://github.com/okonet/lint-staged/releases) - [Commits](https://github.com/okonet/lint-staged/compare/v9.5.0...v10.0.8) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

dependabot-preview[bot]

commit sha c240ae33e81d402b1eaac49ef3128af3a988466d

Bump @types/node from 13.7.4 to 13.7.7 Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 13.7.4 to 13.7.7. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

dependabot-preview[bot]

commit sha b0d012ec9d7e07d089dae4a8d7620be37c581680

Bump @types/mocha from 5.2.7 to 7.0.1 Bumps [@types/mocha](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/mocha) from 5.2.7 to 7.0.1. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/mocha) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

dependabot-preview[bot]

commit sha 1db4986b978bd2d319b7e06c1882dd5265b76f13

Bump mocha from 6.2.2 to 7.1.0 in /server Bumps [mocha](https://github.com/mochajs/mocha) from 6.2.2 to 7.1.0. - [Release notes](https://github.com/mochajs/mocha/releases) - [Changelog](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md) - [Commits](https://github.com/mochajs/mocha/compare/v6.2.2...v7.1.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

dependabot-preview[bot]

commit sha 8dce2b7b2461c59678a6df41cae07004a934e510

Bump typescript from 3.8.2 to 3.8.3 Bumps [typescript](https://github.com/Microsoft/TypeScript) from 3.8.2 to 3.8.3. - [Release notes](https://github.com/Microsoft/TypeScript/releases) - [Commits](https://github.com/Microsoft/TypeScript/compare/v3.8.2...v3.8.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

Pine

commit sha 8f66b998185e006449148f2d6a73b0bbfca9a39e

Merge pull request #1744 from vuejs/dependabot/npm_and_yarn/server/mocha-7.1.0 Bump mocha from 6.2.2 to 7.1.0 in /server

view details

Pine

commit sha faf430ebf4da28a0d1354993c904649354982668

Merge pull request #1695 from vuejs/dependabot/npm_and_yarn/types/mocha-7.0.1 Bump @types/mocha from 5.2.7 to 7.0.1

view details

Pine

commit sha 5066485d48f9d657ffe02ffd2b28e0e19f6feb8a

Merge pull request #1539 from vuejs/dependabot/npm_and_yarn/server/prettier-eslint-9.0.1 Bump prettier-eslint from 8.8.2 to 9.0.1 in /server

view details

Pine

commit sha 8e9f7d5447a5cbc14ea73ecbbc57a95621fa5a35

Merge pull request #1742 from vuejs/dependabot/npm_and_yarn/lint-staged-10.0.8 Bump lint-staged from 9.5.0 to 10.0.8

view details

dependabot-preview[bot]

commit sha 2c6114ebaa61e651ed9902a42d1070f86cc64893

[Security] Bump codecov from 3.6.2 to 3.6.5 in /server Bumps [codecov](https://github.com/codecov/codecov-node) from 3.6.2 to 3.6.5. **This update includes a security fix.** - [Release notes](https://github.com/codecov/codecov-node/releases) - [Commits](https://github.com/codecov/codecov-node/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

Pine Wu

commit sha 910669f1b0bf9411d763bebfd771b52e06f4df1d

Upgrade to LSP V6

view details

Pine Wu

commit sha b6cfa459ac8d7647466ec83bbc8968951f49994e

Add custom data to stylus

view details

Pine Wu

commit sha debf2b54967d5fcb388dabe7767e02ed348179f0

Clean up

view details

Pine Wu

commit sha 4157db827b8d6399cca103dea163ba3d01c3bbae

Changelog

view details

Pine Wu

commit sha df3e1e0a308fc548d3e6fb3f711beda456bb0f0c

Fix tests

view details

push time in 3 months

PR merged 3nuc/vetur

aaa
+4310 -8846

0 comment

161 changed files

3nuc

pr closed time in 3 months

PR opened 3nuc/vetur

aaa
+4310 -8846

0 comment

161 changed files

pr created time in 3 months

more