profile
viewpoint

kaorun343/vue-property-decorator 3344

Vue.js and Property Decorator

kaorun343/vue-typescript-example-2 45

For Vue 2. and TS 2

kaorun343/vue-typescript-example 24

For Vue 1.0 and TS 1.8, not for Vue 2.0 and TS 2.0

kaorun343/vue-photonkit 17

Photonkit components for Vue

kaorun343/vue-typescript-example-4 3

For Vue2.5 and TS 3

kaorun343/vue-class-component 1

ES / TypeScript decorator for class-style Vue components.

kaorun343/vue-rx 1

RxJS integration for Vue.js.

kaorun343/awesome-vue 0

A curated list of awesome things related to Vue.js

kaorun343/DefinitelyTyped 0

The repository for high quality TypeScript type definitions.

startedmaierfelix/nvk

started time in 12 days

startedGoogleChromeLabs/comlink

started time in 14 days

pull request commentkaorun343/vue-property-decorator

Issue # 249: Cannot use @Provide and @ProvideReactive simultaneously.

Please check the latest version, v8.4.0, thanks.

gmoneh

comment created time in 21 days

delete branch kaorun343/monopoly

delete branch : dependabot/npm_and_yarn/handlebars-4.5.3

delete time in 21 days

push eventkaorun343/monopoly

dependabot[bot]

commit sha 67c566bad8fa83d516b7c88c54c15703ab86075e

Bump handlebars from 4.1.2 to 4.5.3 Bumps [handlebars](https://github.com/wycats/handlebars.js) from 4.1.2 to 4.5.3. - [Release notes](https://github.com/wycats/handlebars.js/releases) - [Changelog](https://github.com/wycats/handlebars.js/blob/master/release-notes.md) - [Commits](https://github.com/wycats/handlebars.js/compare/v4.1.2...v4.5.3) Signed-off-by: dependabot[bot] <support@github.com>

view details

kaorun343

commit sha e239f86c17b07131d1024c53e58c4fc0d21b7468

Merge pull request #3 from kaorun343/dependabot/npm_and_yarn/handlebars-4.5.3 Bump handlebars from 4.1.2 to 4.5.3

view details

push time in 21 days

PR merged kaorun343/monopoly

Bump handlebars from 4.1.2 to 4.5.3 dependencies

Bumps handlebars from 4.1.2 to 4.5.3. <details> <summary>Changelog</summary>

Sourced from handlebars's changelog.

v4.5.3 - November 18th, 2019

Bugfixes:

  • fix: add "no-prototype-builtins" eslint-rule and fix all occurences - f7f05d7
  • fix: add more properties required to be enumerable - 1988878

Chores / Build:

  • fix: use !== 0 instead of != 0 - c02b05f
  • add chai and dirty-chai and sinon, for cleaner test-assertions and spies, deprecate old assertion-methods - 93e284e, 886ba86, 0817dad, 93516a0

Security:

  • The properties __proto__, __defineGetter__, __defineSetter__ and __lookupGetter__ have been added to the list of "properties that must be enumerable". If a property by that name is found and not enumerable on its parent, it will silently evaluate to undefined. This is done in both the compiled template and the "lookup"-helper. This will prevent new Remote-Code-Execution exploits that have been published recently.

Compatibility notes:

  • Due to the security-fixes. The semantics of the templates using __proto__, __defineGetter__, __defineSetter__ and __lookupGetter__ in the respect that those expression now return undefined rather than their actual value from the proto.
  • The semantics have not changed in cases where the properties are enumerable, as in:
{
  __proto__: 'some string'
}
  • The change may be breaking in that respect, but we still only increase the patch-version, because the incompatible use-cases are not intended, undocumented and far less important than fixing Remote-Code-Execution exploits on existing systems.

Commits

v4.5.2 - November 13th, 2019

Bugfixes

  • fix: use String(field) in lookup when checking for "constructor" - d541378
  • test: add fluent API for testing Handlebars - c2ac79c

Compatibility notes:

  • no incompatibility are to be expected </tr></table> ... (truncated) </details> <details> <summary>Commits</summary>
  • c819c8b v4.5.3
  • 827c9d0 Update release notes
  • f7f05d7 fix: add "no-prototype-builtins" eslint-rule and fix all occurences
  • 1988878 fix: add more properties required to be enumerable
  • 886ba86 test/chore: add chai/expect and sinon to "runtime"-environment
  • 0817dad test: add sinon as global variable to eslint in the specs
  • 93516a0 test: add sinon.js for spies, deprecate current assertions
  • 93e284e chore: add chai and dirty-chai for better test assertions
  • c02b05f fix: use !== 0 instead of != 0
  • 8de121d v4.5.2
  • Additional commits viewable in compare view </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+3 -3

0 comment

1 changed file

dependabot[bot]

pr closed time in 21 days

issue commentkaorun343/vue-property-decorator

Vue 3.0 support

In my humble opinion, the new api, the composition api is much better than the class style syntax.

webcoderkz

comment created time in 21 days

issue commentkaorun343/vue-property-decorator

Vue 3.0 support

@webcoderkz

Hi. This library depends on vue-class-component. If vue-class-component supports v3.0 and it provides an API for third party libraries including vue-property-decorator, I will continue maintaining this library.

webcoderkz

comment created time in 21 days

issue commentkaorun343/vue-property-decorator

How do I set inheritAttrs to false?

@kpturner

How about this?

import { Vue, Component } from 'vue-property-decorator'

@Component({ inheritAttrs: true })
class YourComponent extends Vue {}
kpturner

comment created time in 21 days

delete branch kaorun343/vue-property-decorator

delete branch : dependabot/npm_and_yarn/handlebars-4.5.3

delete time in 21 days

push eventkaorun343/vue-property-decorator

dependabot[bot]

commit sha 78e3fed8fe25a6595b368f99d2a8235570009538

Bump handlebars from 4.1.2 to 4.5.3 Bumps [handlebars](https://github.com/wycats/handlebars.js) from 4.1.2 to 4.5.3. - [Release notes](https://github.com/wycats/handlebars.js/releases) - [Changelog](https://github.com/wycats/handlebars.js/blob/master/release-notes.md) - [Commits](https://github.com/wycats/handlebars.js/compare/v4.1.2...v4.5.3) Signed-off-by: dependabot[bot] <support@github.com>

view details

kaorun343

commit sha 827c601a75a3ab17a217759a56b7cfbf70db06fd

Merge pull request #293 from kaorun343/dependabot/npm_and_yarn/handlebars-4.5.3 Bump handlebars from 4.1.2 to 4.5.3

view details

push time in 21 days

PR merged kaorun343/vue-property-decorator

Bump handlebars from 4.1.2 to 4.5.3 dependencies

Bumps handlebars from 4.1.2 to 4.5.3. <details> <summary>Changelog</summary>

Sourced from handlebars's changelog.

v4.5.3 - November 18th, 2019

Bugfixes:

  • fix: add "no-prototype-builtins" eslint-rule and fix all occurences - f7f05d7
  • fix: add more properties required to be enumerable - 1988878

Chores / Build:

  • fix: use !== 0 instead of != 0 - c02b05f
  • add chai and dirty-chai and sinon, for cleaner test-assertions and spies, deprecate old assertion-methods - 93e284e, 886ba86, 0817dad, 93516a0

Security:

  • The properties __proto__, __defineGetter__, __defineSetter__ and __lookupGetter__ have been added to the list of "properties that must be enumerable". If a property by that name is found and not enumerable on its parent, it will silently evaluate to undefined. This is done in both the compiled template and the "lookup"-helper. This will prevent new Remote-Code-Execution exploits that have been published recently.

Compatibility notes:

  • Due to the security-fixes. The semantics of the templates using __proto__, __defineGetter__, __defineSetter__ and __lookupGetter__ in the respect that those expression now return undefined rather than their actual value from the proto.
  • The semantics have not changed in cases where the properties are enumerable, as in:
{
  __proto__: 'some string'
}
  • The change may be breaking in that respect, but we still only increase the patch-version, because the incompatible use-cases are not intended, undocumented and far less important than fixing Remote-Code-Execution exploits on existing systems.

Commits

v4.5.2 - November 13th, 2019

Bugfixes

  • fix: use String(field) in lookup when checking for "constructor" - d541378
  • test: add fluent API for testing Handlebars - c2ac79c

Compatibility notes:

  • no incompatibility are to be expected </tr></table> ... (truncated) </details> <details> <summary>Commits</summary>
  • c819c8b v4.5.3
  • 827c9d0 Update release notes
  • f7f05d7 fix: add "no-prototype-builtins" eslint-rule and fix all occurences
  • 1988878 fix: add more properties required to be enumerable
  • 886ba86 test/chore: add chai/expect and sinon to "runtime"-environment
  • 0817dad test: add sinon as global variable to eslint in the specs
  • 93516a0 test: add sinon.js for spies, deprecate current assertions
  • 93e284e chore: add chai and dirty-chai for better test assertions
  • c02b05f fix: use !== 0 instead of != 0
  • 8de121d v4.5.2
  • Additional commits viewable in compare view </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+11 -11

0 comment

1 changed file

dependabot[bot]

pr closed time in 21 days

push eventkaorun343/vue-property-decorator

Jose Manuel Casani Guerra

commit sha b9f0ba86b1b0a58164a19aba07ae82836a6c57a9

Fix Emit decorator Sometimes the Emit decorator return 2 values repeated when the correct is only 1..

view details

Jose Manuel Casani Guerra

commit sha 0fd366cc1403438ef3b4eb2f1e37b7e035e074e4

Fix undefined variable

view details

Jose Manuel Casani Guerra

commit sha 43c5573c27ead5f6d91431d6b089189f81dc4ef9

Prevent override the propertyKey

view details

kaorun343

commit sha 14b5116c464c0a917004bec83a6957c40c2dbdb3

Merge pull request #291 from MrJmpl3/patch-1 Fix Emit decorator

view details

push time in 21 days

PR merged kaorun343/vue-property-decorator

Fix Emit decorator

Sometimes the Emit decorator return 2 values repeated when the correct is only 1..

+15 -4

1 comment

1 changed file

MrJmpl3

pr closed time in 21 days

pull request commentkaorun343/vue-property-decorator

Fix Emit decorator

@MrJmpl3

Hi. Thanks for your PR. I'll merge this.

MrJmpl3

comment created time in 21 days

push eventkaorun343/vue-property-decorator

Den Great

commit sha 4d648352535e416d12011ea462b0636d0a3c4ed5

Don't validate vue property type for TS metadata type Object

view details

kaorun343

commit sha 8d5c9356644e9b09e2282f63b7b17e011a1d07be

Merge pull request #297 from gr8den/master Don't validate vue property type for TS metadata type Object

view details

push time in 21 days

PR merged kaorun343/vue-property-decorator

Don't validate vue property type for TS metadata type Object

fix https://github.com/kaorun343/vue-property-decorator/issues/234

+4 -1

1 comment

1 changed file

gr8den

pr closed time in 21 days

issue closedkaorun343/vue-property-decorator

Prop with type 'any' got [Vue Warn] ... Expected Object,...

when I try to define any type prop like this (with reflect-metadata):

@Prop()
readonly value?: any;

and using like this:

<mdc-list-item :value="1"></mdc-list-item>

then got some [Vue warn] like this: image

it seems like the reflected type is Object when set the type of prop to any, image

so is there any solutions?


I have checked #69, but I'm using the lasted version 8.2.1 and it still doesn't work.

closed time in 21 days

Fonigle

pull request commentkaorun343/vue-property-decorator

Don't validate vue property type for TS metadata type Object

@gr8den

Hi. Thanks for your PR. I'll merge this.

gr8den

comment created time in 21 days

push eventkaorun343/vue-property-decorator

kaorun343

commit sha 83f02972883c86d385012c544f36aaee4cf5516a

v8.4.0

view details

push time in 22 days

push eventkaorun343/nhk-program

dependabot[bot]

commit sha d720ad7244caff850401b2b3a64d30008e521f63

Bump handlebars from 4.1.2 to 4.5.3 Bumps [handlebars](https://github.com/wycats/handlebars.js) from 4.1.2 to 4.5.3. - [Release notes](https://github.com/wycats/handlebars.js/releases) - [Changelog](https://github.com/wycats/handlebars.js/blob/master/release-notes.md) - [Commits](https://github.com/wycats/handlebars.js/compare/v4.1.2...v4.5.3) Signed-off-by: dependabot[bot] <support@github.com>

view details

kaorun343

commit sha cd74908105d8d2b5de62ac4521464c7a7e3ed642

Merge pull request #5 from kaorun343/dependabot/npm_and_yarn/handlebars-4.5.3 Bump handlebars from 4.1.2 to 4.5.3

view details

push time in 22 days

PR merged kaorun343/nhk-program

Bump handlebars from 4.1.2 to 4.5.3 dependencies

Bumps handlebars from 4.1.2 to 4.5.3. <details> <summary>Changelog</summary>

Sourced from handlebars's changelog.

v4.5.3 - November 18th, 2019

Bugfixes:

  • fix: add "no-prototype-builtins" eslint-rule and fix all occurences - f7f05d7
  • fix: add more properties required to be enumerable - 1988878

Chores / Build:

  • fix: use !== 0 instead of != 0 - c02b05f
  • add chai and dirty-chai and sinon, for cleaner test-assertions and spies, deprecate old assertion-methods - 93e284e, 886ba86, 0817dad, 93516a0

Security:

  • The properties __proto__, __defineGetter__, __defineSetter__ and __lookupGetter__ have been added to the list of "properties that must be enumerable". If a property by that name is found and not enumerable on its parent, it will silently evaluate to undefined. This is done in both the compiled template and the "lookup"-helper. This will prevent new Remote-Code-Execution exploits that have been published recently.

Compatibility notes:

  • Due to the security-fixes. The semantics of the templates using __proto__, __defineGetter__, __defineSetter__ and __lookupGetter__ in the respect that those expression now return undefined rather than their actual value from the proto.
  • The semantics have not changed in cases where the properties are enumerable, as in:
{
  __proto__: 'some string'
}
  • The change may be breaking in that respect, but we still only increase the patch-version, because the incompatible use-cases are not intended, undocumented and far less important than fixing Remote-Code-Execution exploits on existing systems.

Commits

v4.5.2 - November 13th, 2019

Bugfixes

  • fix: use String(field) in lookup when checking for "constructor" - d541378
  • test: add fluent API for testing Handlebars - c2ac79c

Compatibility notes:

  • no incompatibility are to be expected </tr></table> ... (truncated) </details> <details> <summary>Commits</summary>
  • c819c8b v4.5.3
  • 827c9d0 Update release notes
  • f7f05d7 fix: add "no-prototype-builtins" eslint-rule and fix all occurences
  • 1988878 fix: add more properties required to be enumerable
  • 886ba86 test/chore: add chai/expect and sinon to "runtime"-environment
  • 0817dad test: add sinon as global variable to eslint in the specs
  • 93516a0 test: add sinon.js for spies, deprecate current assertions
  • 93e284e chore: add chai and dirty-chai for better test assertions
  • c02b05f fix: use !== 0 instead of != 0
  • 8de121d v4.5.2
  • Additional commits viewable in compare view </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+3 -3

0 comment

1 changed file

dependabot[bot]

pr closed time in 22 days

delete branch kaorun343/yargs-test

delete branch : dependabot/npm_and_yarn/handlebars-4.5.3

delete time in 22 days

push eventkaorun343/yargs-test

dependabot[bot]

commit sha edd533ca2601d2a1ee7d14fd07ec8c2c4e2d3545

Bump handlebars from 4.1.2 to 4.5.3 Bumps [handlebars](https://github.com/wycats/handlebars.js) from 4.1.2 to 4.5.3. - [Release notes](https://github.com/wycats/handlebars.js/releases) - [Changelog](https://github.com/wycats/handlebars.js/blob/master/release-notes.md) - [Commits](https://github.com/wycats/handlebars.js/compare/v4.1.2...v4.5.3) Signed-off-by: dependabot[bot] <support@github.com>

view details

kaorun343

commit sha f8f9ba34c5c7734dcf3880c6b8438967f5816d54

Merge pull request #1 from kaorun343/dependabot/npm_and_yarn/handlebars-4.5.3 Bump handlebars from 4.1.2 to 4.5.3

view details

push time in 22 days

PR merged kaorun343/yargs-test

Bump handlebars from 4.1.2 to 4.5.3 dependencies

Bumps handlebars from 4.1.2 to 4.5.3. <details> <summary>Changelog</summary>

Sourced from handlebars's changelog.

v4.5.3 - November 18th, 2019

Bugfixes:

  • fix: add "no-prototype-builtins" eslint-rule and fix all occurences - f7f05d7
  • fix: add more properties required to be enumerable - 1988878

Chores / Build:

  • fix: use !== 0 instead of != 0 - c02b05f
  • add chai and dirty-chai and sinon, for cleaner test-assertions and spies, deprecate old assertion-methods - 93e284e, 886ba86, 0817dad, 93516a0

Security:

  • The properties __proto__, __defineGetter__, __defineSetter__ and __lookupGetter__ have been added to the list of "properties that must be enumerable". If a property by that name is found and not enumerable on its parent, it will silently evaluate to undefined. This is done in both the compiled template and the "lookup"-helper. This will prevent new Remote-Code-Execution exploits that have been published recently.

Compatibility notes:

  • Due to the security-fixes. The semantics of the templates using __proto__, __defineGetter__, __defineSetter__ and __lookupGetter__ in the respect that those expression now return undefined rather than their actual value from the proto.
  • The semantics have not changed in cases where the properties are enumerable, as in:
{
  __proto__: 'some string'
}
  • The change may be breaking in that respect, but we still only increase the patch-version, because the incompatible use-cases are not intended, undocumented and far less important than fixing Remote-Code-Execution exploits on existing systems.

Commits

v4.5.2 - November 13th, 2019

Bugfixes

  • fix: use String(field) in lookup when checking for "constructor" - d541378
  • test: add fluent API for testing Handlebars - c2ac79c

Compatibility notes:

  • no incompatibility are to be expected </tr></table> ... (truncated) </details> <details> <summary>Commits</summary>
  • c819c8b v4.5.3
  • 827c9d0 Update release notes
  • f7f05d7 fix: add "no-prototype-builtins" eslint-rule and fix all occurences
  • 1988878 fix: add more properties required to be enumerable
  • 886ba86 test/chore: add chai/expect and sinon to "runtime"-environment
  • 0817dad test: add sinon as global variable to eslint in the specs
  • 93516a0 test: add sinon.js for spies, deprecate current assertions
  • 93e284e chore: add chai and dirty-chai for better test assertions
  • c02b05f fix: use !== 0 instead of != 0
  • 8de121d v4.5.2
  • Additional commits viewable in compare view </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+33 -14

0 comment

1 changed file

dependabot[bot]

pr closed time in 22 days

startedunboundedsystems/adapt

started time in a month

startedmicrosoft/verona

started time in a month

startedomegasisters/homepage

started time in a month

startednodecg/nodecg

started time in a month

startedant-design/ant-design

started time in 2 months

startedbmcmahen/sancho

started time in 2 months

issue closedkaorun343/vue-property-decorator

@Prop declaration with no options type

I always used to declare props without specify the option type decorator, and It works fine even without import 'reflect-metadata'. So I have 3 questions:

1.What is the difference between:

@Prop() items !: string[]
@Prop() exportType!: string
@Prop() showMenu!: boolean

vs

@Prop(Array) items !: string[]
@Prop(String) exportType!: string
@Prop(Boolean) showMenu!: boolean

2.When should I declare the Prop's type definition? 3.Why is it work to me without the import 'reflect-metadata' import?

Thanks!

closed time in 2 months

Danielg212

issue closedkaorun343/vue-property-decorator

NPM library cannot access `this.$http` which defines in `main.ts`

I've created a library called test-com, and then I created an ts vue app.

main.ts

import Vue from "vue";
import axios from "axios";
Vue.prototype.$http = axios

import TestCom from "test-com";
Vue.use(TestCom)

home.vue

<template>
  <div><test-com/></div>
</template>

TestCom.vue in test-com library

<script lang="ts">
// It works if I use `export default {}`
export default {
  created(){
    console.log(this.$http) // an axios instance
  }
}

// It doesn't work if I use `export default class`
import { Component, Prop, Vue } from 'vue-property-decorator';
@Component({})
export default class TestCom extends Vue {

  created(){
    console.log(this.$http) // undefined
  }
}
</script>

closed time in 2 months

wxs77577

issue commentkaorun343/vue-property-decorator

NPM library cannot access `this.$http` which defines in `main.ts`

@wxs77577 Hi. I apologize you to my late reply.

Could you ask this question at vue-class-component ? This problem is caused by the mechanism of the library.

wxs77577

comment created time in 2 months

pull request commentkaorun343/vue-property-decorator

Update README.md

@bk202 Hi. I apologize you to the late reply. Thanks for you PR.

I would like to emphasize that using reflect-metadata is optional. However, I felt that the new expression enforces users to include the library.

bk202

comment created time in 2 months

push eventkaorun343/vue-property-decorator

G Araya

commit sha 8eeea5d581c69c9eac9547f75f0d95d595a791a0

Issue # 249: Cannot use @Provide and @ProvideReactive simultaneously.

view details

kaorun343

commit sha 1a7ceb0dbb84d4a43b527d510b671bbd95c44dd9

Merge pull request #281 from gmoneh/master Issue # 249: Cannot use @Provide and @ProvideReactive simultaneously.

view details

push time in 2 months

PR merged kaorun343/vue-property-decorator

Issue # 249: Cannot use @Provide and @ProvideReactive simultaneously.

This PR addresses the discussion for issue #249 . There was a previous commit that aimed to address this issue (PR #264 ), but that actually broke it further. The problem arises because both the @Provide and @ProvideReactive decorators are competing to install a provide function in the component options. So whichever one is used first is the one who wins (because of the condition that was there to avoid doing it more than once). The strategy taken in this fix is to have only one possible provide function, which is aware of both regular injections and reactive injections, and will produce the appropriate provide options object with both types of properties. As it is now, this feature is broken in the 8.3.0 release, so hopefully this fix can be approved for a minor number release in the near future. Thanks!

+41 -30

1 comment

1 changed file

gmoneh

pr closed time in 2 months

pull request commentkaorun343/vue-property-decorator

Issue # 249: Cannot use @Provide and @ProvideReactive simultaneously.

@gmoneh

Thanks for your contribution! I'll merge this.

gmoneh

comment created time in 2 months

startedLingDong-/wenyan-lang

started time in 2 months

startedposva/pinia

started time in 2 months

issue closedkaorun343/vue-property-decorator

Is Vue3 supported?

With the new function-based API in VueJS 3, will the property decorators still work?

closed time in 3 months

andreixk

issue commentkaorun343/vue-property-decorator

Is Vue3 supported?

@andreixk Hi. It completely depends on vue-class-component. If it supports the new Vue, this library also do so.

In my opinion, the function-based API is so nice!! I'm really looking forward to use the new API.

andreixk

comment created time in 3 months

fork kaorun343/obs-studio

OBS Studio - Free and open source software for live streaming and screen recording

https://obsproject.com/

fork in 3 months

startedziglang/zig

started time in 3 months

issue commentkaorun343/vue-property-decorator

Need in default way to get types

@viT-1 Hi. Did you meet some problems that caused by the current way of providing the definition file?

viT-1

comment created time in 3 months

startedGoogleChromeLabs/react-adaptive-hooks

started time in 3 months

startedtreosh/lighthouse-ci-action

started time in 3 months

startedreduxjs/reselect

started time in 4 months

issue commentkaorun343/vue-property-decorator

@Prop() with reflect-metadata not generating invalid prop warnings

@sp33dlink Hi. You need to import reflect-metadata by yourself. I've just updated this README, so please check it.

sp33dlink

comment created time in 4 months

push eventkaorun343/vue-property-decorator

kaorun343

commit sha 9aecbd28c53927494f51202c3682632bbeffb6ad

Update README.md

view details

push time in 4 months

issue closedkaorun343/vue-property-decorator

The render function dose not work reactive

Hi, The render function in typescript dose not work as same as in javascript. It was not render again with the data update.

js-example

<template>
  <div>
    <h3>js</h3>
    <p>users: {{ users }}</p>
    <p>dictRole: {{ dictRole }}</p>
    <Table border :columns="columns1" :data="users" width="600"></Table>
  </div>
</template>

<script>
export default {
  data() {
    return {
      columns1: [
        {
          title: "Name",
          key: "name"
        },
        {
          title: "Role",
          key: "role",
          render: (h, params) => {
            const { role } = params.row;
            const { value = role } =
              this.dictRole.find(item => item.key === role) || {};
            console.log("render", this.dictRole.length, value);
            return h("div", value);
          }
        }
      ],
      users: [
        { name: "Tony", role: 0 },
        { name: "Peter", role: 1 },
        { name: "Lisa", role: 0 }
      ],
      dictRole: []
    };
  },
  created() {
    this.getDictRole();
  },
  methods: {
    getDictRole() {
      setTimeout(() => {
        this.dictRole = [
          { key: 0, value: "doctor" },
          { key: 1, value: "teacher" }
        ];
      }, 1200);
    }
  }
};
</script>

ts-example gif

<template>
  <div>
    <h3>ts</h3>
    <p>users: {{ users }}</p>
    <p>dictRole: {{ dictRole }}</p>
    <Table border :columns="columns1" :data="users" width="600"></Table>
  </div>
</template>

<script lang="ts">
import { Vue, Component } from "vue-property-decorator";

@Component
export default class extends Vue {
  columns1 = [
    {
      title: "Name",
      key: "name"
    },
    {
      title: "Role",
      key: "role",
      render: (h, params) => {
        const { role } = params.row;
        const { value = role } =
          this.dictRole.find(item => item.key === role) || {};
        console.log("render", this.dictRole.length, value);
        return h("div", value);
      }
    }
  ];
  users = [
    { name: "Tony", role: 0 },
    { name: "Peter", role: 1 },
    { name: "Lisa", role: 0 }
  ];
  dictRole = [];
  created() {
    this.getDictRole();
  }
  getDictRole() {
    setTimeout(() => {
      this.dictRole = [
        { key: 0, value: "doctor" },
        { key: 1, value: "teacher" }
      ];
    }, 1200);
  }
}
</script>

Here is the expamle links. js example ts example

closed time in 4 months

edtam

issue commentkaorun343/vue-property-decorator

The render function dose not work reactive

@edtam Hi. Could you ask this question at the repository of vue-class-compnent or Vue's official forum? Thanks.

edtam

comment created time in 4 months

delete branch kaorun343/nhk-program

delete branch : dependabot/npm_and_yarn/safer-eval-1.3.5

delete time in 4 months

push eventkaorun343/nhk-program

dependabot[bot]

commit sha a191d58f6c736bae43d8ab41c4ebc88195d82242

Bump safer-eval from 1.3.3 to 1.3.5 Bumps [safer-eval](https://github.com/commenthol/safer-eval) from 1.3.3 to 1.3.5. - [Release notes](https://github.com/commenthol/safer-eval/releases) - [Commits](https://github.com/commenthol/safer-eval/compare/v1.3.3...v1.3.5) Signed-off-by: dependabot[bot] <support@github.com>

view details

kaorun343

commit sha e8c32f220195107db7eb5894d23a20756b95ec71

Merge pull request #4 from kaorun343/dependabot/npm_and_yarn/safer-eval-1.3.5 Bump safer-eval from 1.3.3 to 1.3.5

view details

push time in 4 months

PR merged kaorun343/nhk-program

Bump safer-eval from 1.3.3 to 1.3.5 dependencies

Bumps safer-eval from 1.3.3 to 1.3.5. <details> <summary>Commits</summary>

  • 6d5ed4b 1.3.5
  • fbbc623 Merge pull request #7 from commenthol/strict-mode-recommendation
  • 1a87237 fix: use strict mode recommendation
  • b81dab9 1.3.4
  • 073267a Merge pull request #6 from commenthol/fix-breakout-console
  • 25c3048 docu: Update tested browsers/ node versions
  • 25fbbe5 fix: sandbox breakout with console.constructor...
  • 1ff9411 chore: bump dependencies
  • See full diff in compare view </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+13 -13

0 comment

1 changed file

dependabot[bot]

pr closed time in 4 months

issue closedkaorun343/vue-property-decorator

Error in data(): "TypeError: Cannot read property '$createElement' of undefined"

when i define a jsx variable in vue. the err message appear in browser console. but it works in js file. code like this

<template>
...
</template>
<script lang="tsx">
import { Component, Prop, Vue } from "vue-property-decorator";

@Component
export default class HelloWorld extends Vue {
  @Prop() private msg!: string;
  test = <div></div>;
}
</script>

the compile code like this

...
var HelloWorld =
/*#__PURE__*/
function (_Vue) {
  _inherits(HelloWorld, _Vue);

  function HelloWorld() {
    var _this;

    _classCallCheck(this, HelloWorld);
  
    var h = _this.$createElement;
    _this = _possibleConstructorReturn(this, _getPrototypeOf(HelloWorld).apply(this, arguments));
    _this.test = h("div");
    return _this;
  }

  _createClass(HelloWorld, [{
    key: "mounted",
    value: function mounted() {
      console.log(this, this.$createElement);
    }
  }]);

  return HelloWorld;
}(Vue);

above code shows that h is assigned before _this. I think this is why the problem occured.

closed time in 4 months

we125182

issue commentkaorun343/vue-property-decorator

Error in data(): "TypeError: Cannot read property '$createElement' of undefined"

@we125182

Hi. Could you ask this question at vue-class-component directory or Vue's official forum? Thanks.

we125182

comment created time in 4 months

issue closedkaorun343/vue-property-decorator

Issue with reactivity with getModule

Hi. I am having an issue where properties from states I fetch with getModule are not reactive.

I have a Vuex Store like this;

import Vue from 'vue'
import Vuex from 'vuex'
import  { UserStore } from './user/index'
import {getModule} from "vuex-module-decorators";

Vue.use(Vuex);

interface StoreType {
  UserModule: UserStore,
}

const store = new Vuex.Store<StoreType>({
  modules: {
    UserModule: UserStore
  }
});

export default store;
export const UserModule = getModule(UserStore, store);

UserStore is defined like this;

import {Module, VuexModule, Mutation, Action} from 'vuex-module-decorators'
import User from '@/types/User'
import {SharedModule, UserModule} from "@/store";
import Noty from 'noty';

@Module({
    name: 'UserModule',
})
export class UserStore extends VuexModule {
    user?: User = undefined;

    @Mutation setUser(user: User) {
        this.user = user;
    }

    @Action
    signUserInWithEmailAndPassword(request: SignInWithEmailAndPasswordRequest) {
        ...
        this.setUser(newUser);
        ...
    }
}

And I use it in my component like this;

    import {Watch} from "vue-property-decorator";
    import Vue from "vue";
    import {UserModule} from "@/store";
    import Component from "vue-class-component";
    import User from "@/types/User";

    interface ISignIn {
        user: User | undefined;
    }

    @Component({
        name: 'SignIn'
    })

    export default class SignIn extends Vue implements ISignIn {
        get user() {
            // This is not reactive
            return UserModule.user;
            // This is reactive
            return this.$store.state.UserModule.user
        }
    }

Am I doing anything wrong here? Why is the module as fetched with getModule and imported reactive? Is there any way to fix this?

closed time in 4 months

smholsen

issue commentkaorun343/vue-property-decorator

Issue with reactivity with getModule

@smholsen Hi. Could you ask this question at vuex-module-decorators repository? It seems this issue isn't related to this library.

smholsen

comment created time in 4 months

delete branch kaorun343/vue-property-decorator

delete branch : dependabot/npm_and_yarn/mixin-deep-1.3.2

delete time in 4 months

PR merged kaorun343/vue-property-decorator

Bump mixin-deep from 1.3.1 to 1.3.2 dependencies

Bumps mixin-deep from 1.3.1 to 1.3.2. <details> <summary>Commits</summary>

  • 754f0c2 1.3.2
  • 90ee1fa ensure keys are valid when mixing in values
  • See full diff in compare view </details> <details> <summary>Maintainer changes</summary>

This version was pushed to npm by doowb, a new releaser for mixin-deep since your current version. </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+7 -2

0 comment

1 changed file

dependabot[bot]

pr closed time in 4 months

push eventkaorun343/vue-property-decorator

dependabot[bot]

commit sha 9413e38de07630f39c67bad7500c84be97dff732

Bump mixin-deep from 1.3.1 to 1.3.2 Bumps [mixin-deep](https://github.com/jonschlinkert/mixin-deep) from 1.3.1 to 1.3.2. - [Release notes](https://github.com/jonschlinkert/mixin-deep/releases) - [Commits](https://github.com/jonschlinkert/mixin-deep/compare/1.3.1...1.3.2) Signed-off-by: dependabot[bot] <support@github.com>

view details

kaorun343

commit sha b917692b452d0ccabbef6c382e595c032718f112

Merge pull request #270 from kaorun343/dependabot/npm_and_yarn/mixin-deep-1.3.2 Bump mixin-deep from 1.3.1 to 1.3.2

view details

push time in 4 months

release kaorun343/vue-property-decorator

v8.3.0

released time in 4 months

created tagkaorun343/vue-property-decorator

tagv8.3.0

Vue.js and Property Decorator

created time in 4 months

push eventkaorun343/vue-property-decorator

kaorun343

commit sha 708c79da03f639bb392ee1194d4327261f2f32c2

v8.3.0 - Update vue-class-component #266 #262 - Fix Provide/ProvideReactive compatibility #264 #249

view details

push time in 4 months

startedpull-stream/pull-stream

started time in 4 months

fork kaorun343/ojichat

おじさんがLINEやメールで送ってきそうな文を生成する

fork in 4 months

startedgreymd/ojichat

started time in 5 months

startedunisonweb/unison

started time in 5 months

push eventkaorun343/vue-property-decorator

oguimbal

commit sha 88b82aa3e9f2abc6b204a76b6729086069b7ec8e

Fix reactive inheritance issue

view details

oguimbal

commit sha 95540e451cb9446411ec945932d0c6e705a32296

small fix

view details

kaorun343

commit sha f30c010e76ef4918311f0715e534fed3eb66cc5b

Merge pull request #265 from oguimbal/master Fix @ProvideReactive() inheritance issue

view details

push time in 5 months

PR merged kaorun343/vue-property-decorator

Fix @ProvideReactive() inheritance issue

See the new test in ProvideReactive.spec.ts, but long story short: Using @ProvideReactive() in a child component overrides all parent dependencies provided using the same method.

For instance, when:

  • Component A provides 'X'
  • Component B, child of A, provides 'Y'
  • Component C uses both 'X' & 'Y'

Then 'Y' is injected, but not 'X'.

This commit fixes it (& adds some test to check that this scenario works for both @Provide and @ProvideReactive

+68 -5

1 comment

3 changed files

oguimbal

pr closed time in 5 months

pull request commentkaorun343/vue-property-decorator

Fix @ProvideReactive() inheritance issue

@oguimbal Hi. Thanks for your PR!!! I'll merge this.

oguimbal

comment created time in 5 months

push eventkaorun343/vue-property-decorator

Lorenzo Millucci

commit sha 7cb72bd8ae38ac9a4ba0233d59e85c43e9105e8d

Issue #262: update vue-class-component

view details

kaorun343

commit sha 25780f8fbaa63cd1f66b870af7ecf85ebf984a23

Merge pull request #266 from lmillucci/262-update-vue-class-component Issue #262: update vue-class-component

view details

push time in 5 months

PR merged kaorun343/vue-property-decorator

Issue #262: update vue-class-component

Update outdated vue-class-component. See https://github.com/kaorun343/vue-property-decorator/issues/262

+5 -5

1 comment

2 changed files

lmillucci

pr closed time in 5 months

pull request commentkaorun343/vue-property-decorator

Issue #262: update vue-class-component

@lmillucci Hi. Thanks for your PR! I'll merge this.

lmillucci

comment created time in 5 months

startedakameco/styled-style

started time in 5 months

startedrambaut/figtree

started time in 5 months

push eventkaorun343/vue-property-decorator

oguimbal

commit sha eedebf4c0415efb57a5304fab9cc069edd46dbcc

Fix Provide/ProvideReactive compatibility (#249)

view details

oguimbal

commit sha 48ab645b3f29bf5b11f2b91d19b8d1d5d4721dd1

Add unit test

view details

kaorun343

commit sha 97735df254ca40d9b5df257127872c2edc5c1d49

Merge pull request #264 from oguimbal/master Fix Provide/ProvideReactive compatibility (#249)

view details

push time in 5 months

PR merged kaorun343/vue-property-decorator

Fix Provide/ProvideReactive compatibility (#249)

@Provide() and @ProvideReactive() were not compatible. ... they are now. See #249

+51 -9

1 comment

2 changed files

oguimbal

pr closed time in 5 months

pull request commentkaorun343/vue-property-decorator

Fix Provide/ProvideReactive compatibility (#249)

@oguimbal

Hi! Thanks for your PR!! I really appreciate for you. I'll merge this.

oguimbal

comment created time in 5 months

startedmbrn/material-table

started time in 5 months

startedbvaughn/react-window

started time in 5 months

startednodegui/nodegui

started time in 5 months

startedrust-lang-nursery/packed_simd

started time in 6 months

more