owner stringclasses 14
values | repo stringclasses 14
values | id int64 116k 4.61B | issue_number int32 1 181k | author stringlengths 1 39 | body stringlengths 1 262k | created_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:16:18 | updated_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:22:56 | reactions unknown | author_association stringclasses 5
values |
|---|---|---|---|---|---|---|---|---|---|
vuejs | core | 622,547,981 | 1,083 | yyx990803 | I think it's expected behavior to require `libs: ['dom']` when using `vue` since it is expected to work in DOM environments.
What we can improve is that `UnwrapRef` is declared in `@vue/reactivity` which should not assume the end environment it's running in. This could cause issues for custom renderers. | 2020-05-01T20:15:22 | 2020-05-01T20:15:22 | {
"+1": 1
} | MEMBER |
vuejs | core | 622,958,484 | 1,033 | elevatebart | @martinoppitz I do not understand. Do you mean that preact typings are different from react typings?
What do you suggest I do in a monorepo that has both react and Vuejs ? | 2020-05-02T14:02:25 | 2020-05-02T14:02:25 | {} | CONTRIBUTOR |
vuejs | core | 623,342,758 | 1,107 | sionzee | This should be deployed ASAP, beta7 is unusable because of this.
I have got thousands errors.
In meantime downgraded to beta6. | 2020-05-04T08:56:25 | 2020-05-04T08:56:25 | {} | NONE |
vuejs | core | 623,491,690 | 1,118 | underfin | I try do this with master branch code.It is correct behavior with 3.0.0-beta.6.Please wait next version publish.
| 2020-05-04T14:17:45 | 2020-05-04T14:17:45 | {
"+1": 1
} | MEMBER |
vuejs | core | 623,616,106 | 1,114 | zuozuomuxi | @leopiccionia @yyx990803 For TS developers, props must be declared in two places?
```ts
interface MyProps {
label: string;
}
export default {
props: {
label: String
},
setup(props: MyProps) {
// ...
},
};
```
This is very bad for me, hope to have a better solution. | 2020-05-04T18:02:33 | 2020-05-04T18:02:33 | {
"+1": 3
} | NONE |
vuejs | core | 626,550,831 | 1,159 | posva | Can you fix the repro please and update the steps to reproduce (what to do to show the problem). Here is your repro fixed so it runs: https://jsfiddle.net/posva/94ktc5eq/ | 2020-05-11T08:22:08 | 2020-05-11T08:22:08 | {} | MEMBER |
vuejs | core | 626,567,611 | 1,137 | dependabot-preview[bot] | Superseded by #1163. | 2020-05-11T08:54:50 | 2020-05-11T08:54:50 | {} | CONTRIBUTOR |
vuejs | core | 626,791,503 | 1,151 | yyx990803 | The reason your tests were failing inconsistently is because we are testing by talking to Puppeteer so everything is async and may or may not be longer than the actual microtask inside Puppeteer. So when you `await click('button')`, the microtask may have already fired so you won't be able get the transition start stat... | 2020-05-11T15:56:16 | 2020-05-11T15:56:16 | {
"+1": 2
} | MEMBER |
vuejs | core | 622,661,325 | 1,101 | yyx990803 | This is intentional because switch is faster. | 2020-05-02T03:21:23 | 2020-05-02T03:21:23 | {} | MEMBER |
vuejs | core | 623,006,155 | 1,033 | elevatebart | Thank you @martinoppitz,
I understand your disliking for monorepos. They can create monoliths that are long to clone and even longer to install.
In our case though, the vue-next monorepo could save our bacon. It allows easy extraction of a package in a PR. Once the PR is accepted, all 3 modified packages are deli... | 2020-05-02T20:01:39 | 2020-05-02T20:01:39 | {} | CONTRIBUTOR |
vuejs | core | 623,071,645 | 626 | dolymood | Bump to TS 3.9 is very necessary. I will try to update codes to compatible with TS 3.9. | 2020-05-03T08:03:09 | 2020-05-03T08:03:09 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 623,259,255 | 1,098 | liulinboyi | Hello, you can pull the latest code, and re-push or force push, to trigger and pass the check | 2020-05-04T05:06:41 | 2020-05-04T05:06:41 | {} | MEMBER |
vuejs | core | 623,531,173 | 1,106 | pikax | That's great! will try that out and update this :) Thanks! | 2020-05-04T15:25:27 | 2020-05-04T15:25:27 | {} | MEMBER |
vuejs | core | 624,613,522 | 1,128 | posva | @gzzhanghao Please give more details next time you open an issue: be precise about what is expected and missing like the attribute name. without the second comment, it is very difficult to understand.
You are setting an HTML attribute, so it makes sense it is set as an attribute. Props are set as props when using `v... | 2020-05-06T12:14:32 | 2020-05-06T12:14:32 | {} | MEMBER |
vuejs | core | 624,738,232 | 1,135 | yyx990803 | It should still attempt the write to trigger the warning. Otherwise it just fails silently. | 2020-05-06T16:03:05 | 2020-05-06T16:03:05 | {} | MEMBER |
vuejs | core | 625,795,585 | 1,145 | underfin | If it is need to fix.I will pull a pr. | 2020-05-08T12:38:53 | 2020-05-08T12:38:53 | {} | MEMBER |
vuejs | core | 626,371,924 | 1,156 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2020-05-10T18:50:37 | 2020-05-10T18:50:37 | {} | CONTRIBUTOR |
vuejs | core | 622,591,257 | 1,097 | posva | See https://github.com/vuejs/rfcs/blob/master/active-rfcs/0009-global-api-change.md | 2020-05-01T22:22:30 | 2020-05-01T22:22:30 | {} | MEMBER |
vuejs | core | 623,383,104 | 1,117 | pikax | @dependabot squash and merge | 2020-05-04T10:24:57 | 2020-05-04T10:24:57 | {} | MEMBER |
vuejs | core | 624,206,865 | 1,122 | LinusBorg | Hi!
It seems you opened this in the wrong repository because you are misunderstanding who supports what.
Therefore:
* Vue 3 will not support apollo directly, and never has.
* vue-apollo is a plugin for Vue
* `vue-apollo` will support Vue 3, and right now, it has to keep up with changes in the beta.
* If it d... | 2020-05-05T17:46:32 | 2020-05-05T17:50:02 | {
"heart": 2
} | MEMBER |
vuejs | core | 625,687,622 | 1,137 | pikax | This will be fixed in the next minor: https://github.com/kulshekhar/ts-jest/issues/1604#issuecomment-625057731 | 2020-05-08T07:46:36 | 2020-05-08T07:46:36 | {} | MEMBER |
vuejs | core | 623,050,340 | 1,080 | xland | @thecrypticace
I'm sorry to bother you again.
Have you noticed this phenomenon?
`onMounted` event in a grandchild component's setup function is fired too early.
Code:
In the grandparent component's tem... | 2020-05-03T03:58:47 | 2020-05-03T03:58:47 | {} | NONE |
vuejs | core | 623,051,442 | 1,080 | thecrypticace | Could you please file a separate issue with a reproduction link? It's hard for me to see the structure of your app and what the potential problem is from the screenshot and code above. | 2020-05-03T04:15:46 | 2020-05-03T04:15:46 | {} | CONTRIBUTOR |
vuejs | core | 623,311,109 | 1,060 | basvanmeurs | That's awesome. Thanks! | 2020-05-04T07:48:23 | 2020-05-04T07:48:23 | {} | CONTRIBUTOR |
vuejs | core | 624,517,784 | 1,129 | ktsn | Hmm, I realized this is tougher than I thought. Making `ref.value` type to be the base type of generics wouldn't solve the issue completely as it mismatches if we want to assign it to another generics typed value.
```ts
function useState<State extends string>(initial: State) {
const state = ref(initial) // state... | 2020-05-06T08:40:49 | 2020-05-06T08:40:49 | {} | CONTRIBUTOR |
vuejs | core | 626,111,037 | 1,144 | underfin | Increase transiton time will be work with this. | 2020-05-09T05:50:07 | 2020-05-09T05:50:07 | {} | MEMBER |
vuejs | core | 626,373,597 | 1,157 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2020-05-10T19:02:46 | 2020-05-10T19:02:46 | {} | CONTRIBUTOR |
vuejs | core | 626,811,119 | 1,152 | yyx990803 | I think this is good enough - `BaseTransition` does not have the concept of classes since it's platform agnostic. | 2020-05-11T16:30:38 | 2020-05-11T16:30:38 | {} | MEMBER |
vuejs | core | 623,267,311 | 1,111 | LinusBorg | Seems it interprets the `foo` object as a ref because of the `value` property. If it's renamed, it doesn't happen anymore.
That problem has been fixed before, Ref's have a special marker attribute to prevent that from happening.
Thanks for reporting, we'll look into it!
| 2020-05-04T05:40:17 | 2020-05-04T05:40:17 | {} | MEMBER |
vuejs | core | 623,383,274 | 1,117 | pikax | @dependabot rebase | 2020-05-04T10:25:19 | 2020-05-04T10:25:19 | {
"+1": 1
} | MEMBER |
vuejs | core | 623,450,999 | 1,118 | underfin | Fix the typo.Use `<Foo ref="foo" />` instead of ` <Foo ref="roo" />` | 2020-05-04T13:04:13 | 2020-05-04T13:04:13 | {
"+1": 1
} | MEMBER |
vuejs | core | 623,571,645 | 1,100 | AlexandreBonaventure | no worries, thanks for cleaning it up! | 2020-05-04T16:36:03 | 2020-05-04T16:36:03 | {} | CONTRIBUTOR |
vuejs | core | 623,621,051 | 1,114 | jacekkarczmarczyk | just `setup(props)`, type of `props` will be inferred | 2020-05-04T18:11:59 | 2020-05-04T18:11:59 | {} | CONTRIBUTOR |
vuejs | core | 623,810,646 | 1,121 | aztalbot | I think you need a function ref. From the composition api reference:
https://composition-api.vuejs.org/api.html#template-refs
> Composition API template refs do not have special handling when used inside v-for. Instead, use function refs (new feature in 3.0) to perform custom handling | 2020-05-05T03:14:05 | 2020-05-05T03:14:05 | {} | CONTRIBUTOR |
vuejs | core | 624,471,622 | 1,126 | underfin | You can try merge two `v-for` into one , like the blow code , hope this help you.
```
<article
v-for="todo in todos"
:key="todo.id"
:class="[todo.done ? 'column-right' : 'column-left']"
class="todo column-left"
@click="todo.done = !todo.done"
>
// xxx
</article>
``... | 2020-05-06T06:44:49 | 2020-05-06T06:44:49 | {} | MEMBER |
vuejs | core | 624,546,879 | 1,128 | gzzhanghao | @underfin The `indeterminate` property on the input element should be a DOM property, but it was set as an attribute here.
See: https://stackoverflow.com/q/9366087 | 2020-05-06T09:43:51 | 2020-05-06T09:43:51 | {} | CONTRIBUTOR |
vuejs | core | 625,316,864 | 1,140 | underfin | @yyx990803 .It is some error with this.I write message to later. | 2020-05-07T15:14:11 | 2020-05-07T15:14:11 | {} | MEMBER |
vuejs | core | 626,134,845 | 1,145 | underfin | I re-think this. Maybe this change is not break user upgarde v3.So can we just do this? | 2020-05-09T09:16:05 | 2020-05-09T09:16:05 | {} | MEMBER |
vuejs | core | 626,791,773 | 1,151 | yyx990803 | See https://github.com/vuejs/vue-next/commit/9d111f534adfea77e106f7f5054a842b3c0b26de for the fixed version. | 2020-05-11T15:56:40 | 2020-05-11T15:56:40 | {} | MEMBER |
vuejs | core | 599,159,226 | 836 | jbruni | The array syntax for `ref` is not an issue when used in `createBlock`, because `props` type is defined as [`{ [key: string]: any } | null`](https://github.com/vuejs/vue-next/blob/v3.0.0-alpha.8/packages/runtime-core/src/vnode.ts#L166)...
Now I see :thinking: ...
It looks like `createBlock`'s props argument type s... | 2020-03-15T02:27:24 | 2020-03-15T02:35:54 | {} | NONE |
vuejs | core | 601,422,685 | 855 | loeffel-io | Thank you for your support! | 2020-03-19T21:20:49 | 2020-03-19T21:20:49 | {} | CONTRIBUTOR |
vuejs | core | 596,791,568 | 580 | yyx990803 | Thanks for the PR but
1. This doesn't account for the case where `lowQueue` doesn't get drained after the timeout. This will result in more and more jobs getting piled up in the `lowQueue` and never gets flushed and leads to inconsistency between the state and the DOM.
2. If a non-empty `lowQueue` leads to an asy... | 2020-03-09T21:36:08 | 2020-03-09T21:36:08 | {
"+1": 1
} | MEMBER |
vuejs | core | 596,792,683 | 504 | yyx990803 | Thanks again for the PR - see #699 | 2020-03-09T21:39:07 | 2020-03-09T21:39:07 | {} | MEMBER |
vuejs | core | 597,431,516 | 813 | LastHeaven | I tryed to use the `.stop`,but it seems not work。
```vue
<template>
<button @click.stop="onClick"><slot/></button>
</template>
<script>
export default {
name: 'MButton',
setup (props, { emit }) {
return {
onClick () {
emit('click')
}
}
}
}
</script>
``` | 2020-03-11T03:55:07 | 2020-03-11T03:55:07 | {} | NONE |
vuejs | core | 597,868,906 | 818 | yyx990803 | This seems unnecessary to me. Cost of checking an empty block node is quite cheap and close to the work being done here. | 2020-03-11T20:42:47 | 2020-03-11T20:42:47 | {} | MEMBER |
vuejs | core | 597,951,108 | 730 | jods4 | @yyx990803 It's still broken in alpha.8. | 2020-03-12T00:48:29 | 2020-03-12T00:48:29 | {} | CONTRIBUTOR |
vuejs | core | 597,969,752 | 815 | KaelWD | You can use `mergeProps` to add event listeners to a vnode. | 2020-03-12T02:05:53 | 2020-03-12T02:05:53 | {} | CONTRIBUTOR |
vuejs | core | 595,134,751 | 791 | hareku | @yyx990803 Could you merge this? | 2020-03-05T09:53:22 | 2020-03-05T09:53:22 | {} | CONTRIBUTOR |
vuejs | core | 596,793,224 | 382 | yyx990803 | Sorry, merged #699 before coming back to this one. Still, thanks for the PR! | 2020-03-09T21:40:36 | 2020-03-09T21:40:36 | {
"+1": 1
} | MEMBER |
vuejs | core | 598,206,811 | 826 | underfin | It doesn't work with this?
```
setup() {
return () => h(customComponent, { text: 'this is a component!' })
}
``` | 2020-03-12T14:10:07 | 2020-03-12T14:10:07 | {} | MEMBER |
vuejs | core | 600,045,490 | 848 | Jimmysh | @djy0 Thanks.
Config webpack success for me. | 2020-03-17T12:33:06 | 2020-03-17T12:33:06 | {} | NONE |
vuejs | core | 600,113,731 | 849 | yyx990803 | I think it should at least support globs in the directories:
``` yml
ls:
packages/**/src:
.ts: camelCase | PascalCase
``` | 2020-03-17T14:51:10 | 2020-03-17T14:51:10 | {} | MEMBER |
vuejs | core | 593,115,142 | 789 | ysj16 | If set dynamicProps a plain array when no dynamic props in transformElement will skip component's props patch, but I don't if it deserves. | 2020-03-01T16:19:51 | 2020-03-01T16:19:51 | {} | CONTRIBUTOR |
vuejs | core | 593,391,778 | 673 | jods4 | I'm closing this issue because I don't think there's more to say about it.
With access to `@vue/reactivity`, it's really easy to build an array that only tracks read/writes globally. Using one more simple api not shown in the benchmark it is 33% to 50% faster than Vuejs built-in array, depending on size.
I think ... | 2020-03-02T13:05:44 | 2020-03-02T13:05:44 | {} | CONTRIBUTOR |
vuejs | core | 596,781,637 | 706 | yyx990803 | Thanks for the PR - but these tests should be narrower in scope and not involve reactive, blocks or patchFlags (blocks and patchFlags should be tested in `rendererOptimizedMode` instead, feel free to work on that one instead)
Also see #699 | 2020-03-09T21:12:05 | 2020-03-09T21:12:05 | {} | MEMBER |
vuejs | core | 597,422,968 | 813 | LastHeaven | # Using custom components triggers the click event twice
### Version
3.0.0-alpha.8
### Reproduction link
none，not support
### Steps to reproduce
Create a component named `MButton`
```vue
<template>
<button @click="onClick"><slot/></button>
</template>
<script>
export default {
name: 'MBut... | 2020-03-11T03:16:06 | 2020-03-11T03:16:06 | {} | NONE |
vuejs | core | 600,120,679 | 849 | loeffel-io | alright, i will work on both features 👍 | 2020-03-17T15:04:06 | 2020-03-17T15:04:06 | {} | CONTRIBUTOR |
vuejs | core | 600,874,860 | 849 | loeffel-io | Just ping me if there is anything i can do! | 2020-03-18T21:46:01 | 2020-03-18T21:46:01 | {} | CONTRIBUTOR |
vuejs | core | 593,249,753 | 641 | himself65 | I think this issue has fixed in the latest version. | 2020-03-02T06:56:54 | 2020-03-02T06:56:54 | {} | CONTRIBUTOR |
vuejs | core | 593,387,797 | 661 | jods4 | I understand why you don't want to add code that is not supported by all browsers at this point (68% according to caniuse https://caniuse.com/#feat=mdn-api_htmlelement_inert) and there is a workaround: I can use a derived `<transition>` component that adds `inert`.
So I'm closing the issue. | 2020-03-02T12:55:34 | 2020-03-02T12:55:34 | {} | CONTRIBUTOR |
vuejs | core | 599,709,599 | 836 | yyx990803 | I did some refactor to remove the need for the special case. | 2020-03-16T19:03:04 | 2020-03-16T19:03:04 | {
"+1": 1,
"hooray": 2
} | MEMBER |
vuejs | core | 600,863,591 | 849 | loeffel-io | For sure, combining cases could be a feature in the next versions, i will think about that some time.
Cool, i will create a pr now 👍 | 2020-03-18T21:17:59 | 2020-03-18T21:17:59 | {} | CONTRIBUTOR |
vuejs | core | 601,694,066 | 853 | yyx990803 | Yes you're right. | 2020-03-20T13:14:38 | 2020-03-20T13:14:38 | {} | MEMBER |
vuejs | core | 593,390,421 | 641 | leopiccionia | @Himself65 Indeed, it's fixed if I upgrade to `3.0.0-alpha.7` and use `shallowRef` instead of `ref`. | 2020-03-02T13:02:34 | 2020-03-02T13:02:34 | {} | CONTRIBUTOR |
vuejs | core | 595,910,167 | 805 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2020-03-06T18:55:38 | 2020-03-06T18:55:38 | {} | CONTRIBUTOR |
vuejs | core | 597,430,242 | 813 | LastHeaven | @underfin Is this a new feature?It's diffrence from vue2. | 2020-03-11T03:49:14 | 2020-03-11T03:49:14 | {} | NONE |
vuejs | core | 599,766,114 | 660 | yyx990803 | Closing the original issue since a `ref` will always be required to use refs. | 2020-03-16T21:27:37 | 2020-03-16T21:27:37 | {} | MEMBER |
vuejs | core | 599,809,410 | 843 | jods4 | @yyx990803 I just noticed another issue with the boolean conversion that my PR didn't fix.
Code works properly but both tests and runtime produce the following warning:
```
Invalid prop: type check failed for prop "active". Expected Boolean, got String with value "".
``` | 2020-03-16T23:54:19 | 2020-03-16T23:54:19 | {} | CONTRIBUTOR |
vuejs | core | 600,067,577 | 660 | yyx990803 | Because the user may do this:
``` js
const state = {
foo: null
}
onMounted(() => {
state.foo // expect to get a ref but won't, because local `state` is not reactive
})
return state
```
A `ref` is more consistent and more explicit. | 2020-03-17T13:21:49 | 2020-03-17T13:22:03 | {} | MEMBER |
vuejs | core | 600,602,836 | 851 | lmiller1990 | Great progress! I think we will need to update `src/index.ts` to export this:
```diff
export {
h,
+ resetTransformHArgs,
+ transformHArgs
} from './h'
```
Then we can just do `import { transformHArgs } from 'vue'`. Unless we don't want to expose this so easily?
_______
No luck using this so... | 2020-03-18T12:46:51 | 2020-03-18T12:59:44 | {} | MEMBER |
vuejs | core | 601,500,874 | 857 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2020-03-20T02:33:49 | 2020-03-20T02:33:49 | {} | CONTRIBUTOR |
vuejs | core | 595,148,898 | 736 | hareku | reopen https://github.com/vuejs/vue-next/pull/798 | 2020-03-05T10:20:27 | 2020-03-05T10:20:27 | {} | CONTRIBUTOR |
vuejs | core | 596,758,749 | 803 | yyx990803 | Closing (commit released in alpha.8) | 2020-03-09T20:18:58 | 2020-03-09T20:19:13 | {} | MEMBER |
vuejs | core | 597,430,288 | 814 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2020-03-11T03:49:25 | 2020-03-11T03:49:25 | {} | CONTRIBUTOR |
vuejs | core | 597,457,157 | 815 | KaelWD | Duplicate of vuejs/vue#9580
You can do this but I'm not sure if there's a built-in way to then render the vnode in the template, you'd have to use a render function.
```js
const slot = computed(() => slots.default())
onMounted(() => console.log(slot[0].el))
return { slot }
``` | 2020-03-11T05:55:25 | 2020-03-11T06:09:57 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 599,158,588 | 835 | jiangying000 | fix: #681
related pr: #794 | 2020-03-15T02:18:22 | 2020-03-15T02:18:22 | {} | CONTRIBUTOR |
vuejs | core | 600,085,127 | 849 | loeffel-io | Thanks for your answer, i appreciate it | 2020-03-17T13:56:00 | 2020-03-17T13:56:00 | {} | CONTRIBUTOR |
vuejs | core | 600,085,255 | 849 | yyx990803 | I think I'd consider adopting it if we can simplify the config to something like:
``` yml
packages/**/(src|tests)/**: camelCase | PascalCase
packages/**/dist/**: kebab-case
```
Essentially
1. Allow glob patterns
2. Allow combining multiple allowed cases | 2020-03-17T13:56:15 | 2020-03-17T13:57:25 | {} | MEMBER |
vuejs | core | 601,408,044 | 853 | yyx990803 | For `v-if` it actually has to always be a block regardless of type to keep the parent's dynamic children list stable. | 2020-03-19T20:45:05 | 2020-03-19T20:45:05 | {} | MEMBER |
vuejs | core | 601,793,105 | 859 | rigor789 | https://github.com/jsdelivr/jsdelivr/issues/18169 | 2020-03-20T16:30:40 | 2020-03-20T16:30:40 | {} | CONTRIBUTOR |
vuejs | core | 593,177,888 | 789 | yyx990803 | Thanks for the PR... But the cost of a full diff will be cheaper than doing all this. | 2020-03-02T01:15:28 | 2020-03-02T01:15:28 | {
"+1": 1
} | MEMBER |
vuejs | core | 595,845,986 | 793 | yyx990803 | `estree-walker` is still needed. Only `@babel/parser` is inlined. | 2020-03-06T16:23:57 | 2020-03-06T16:23:57 | {} | MEMBER |
vuejs | core | 595,865,658 | 798 | yyx990803 | Maybe `unknown` is better here. | 2020-03-06T17:05:24 | 2020-03-06T17:05:24 | {} | MEMBER |
vuejs | core | 596,121,198 | 802 | filonik | I just want to add that I have a "working" proof-of-concept implementation, but due to my lack of familiarity with the internals of Vue, I am not confident enough to create a pull request. However, I am more than happy to share the details if there is interest.
Essentially, it boils down to one change, adding TypedA... | 2020-03-07T17:59:39 | 2020-03-07T19:47:35 | {} | NONE |
vuejs | core | 599,116,114 | 834 | jods4 | One test is failing in CI but it's not related to my changes, it's the `markdown` spec in examples. | 2020-03-14T18:26:09 | 2020-03-14T18:26:09 | {} | CONTRIBUTOR |
vuejs | core | 600,541,409 | 721 | yyyanghj | > If its a function it would just run it without arguments and get the object returned. from there on everything is like it is today.
By the example, Vue can't recognize it is just a `function` or a `function component`
```
// just function
const createAuthenticateUser = (
authenticateUser = AuthenticateUser
... | 2020-03-18T10:25:47 | 2020-03-18T10:25:47 | {} | CONTRIBUTOR |
vuejs | core | 597,430,511 | 813 | LastHeaven | And version 3.0.0-alpha.7 is fine. | 2020-03-11T03:50:20 | 2020-03-11T03:50:20 | {} | NONE |
vuejs | core | 599,006,211 | 831 | hareku | @sqal
> Functional components have no implicit attrs fallthrough behavior.
That is Vue 2.x behavior, but in alpha.8, implicit attrs fallthrough works for both stateful and functional components.
> Implicit fallthrough now works consistently for both stateful and functional components (as long as the compone... | 2020-03-14T03:48:29 | 2020-03-14T03:48:53 | {} | CONTRIBUTOR |
vuejs | core | 600,082,857 | 849 | yyx990803 | Thanks for the PR, but I'm not sure if this actually simplifies or complicates the development process. Creating new files is pretty rare, and looking at the config file it seems there are many special cases - I'm afraid we will mostly end up tweaking the config to make it pass more than it helping us find wrong file n... | 2020-03-17T13:51:25 | 2020-03-17T13:51:25 | {} | MEMBER |
vuejs | core | 600,828,535 | 854 | yyx990803 | This is expected behavior. | 2020-03-18T19:54:08 | 2020-03-18T19:54:08 | {} | MEMBER |
vuejs | core | 595,850,046 | 774 | yyx990803 | Thanks for the PR, see a306658 for a simpler check.
Also, in future PRs, please be more specific on what the desired behavior is and what you are fixing. It would also be nice to include a test case. | 2020-03-06T16:32:16 | 2020-03-06T16:32:16 | {} | MEMBER |
vuejs | core | 599,224,739 | 838 | yyx990803 | 根本原因是 TS 目前无法支持 `.vue` 的 import typing。这个不是 Vue 的实现能解决的问题，不过我们有跟 TS 团队提过这个需求，以后还是有可能支持的。
另外，父组件调用子组件方法基本上是个反模式，能不用就别用。 | 2020-03-15T15:26:08 | 2020-03-15T15:26:08 | {
"+1": 1
} | MEMBER |
vuejs | core | 600,082,179 | 847 | jods4 | That is strange, I must have done something silly. My tsconfig is very strict, though:
https://github.com/jods4/vue-toys/blob/master/tsconfig.json
I had a simple file like the gist to reproduce the problem in there but I didn't commit it. The actual "in context" problem is here:
https://github.com/jods4/vue-toys/b... | 2020-03-17T13:49:58 | 2020-03-17T13:49:58 | {} | CONTRIBUTOR |
vuejs | core | 600,106,815 | 849 | loeffel-io | Thanks @yyx990803,
i can implement these features today!
First of all: Extension declarations like `.ts` or `.js` are necessary.
What do you think about this solution (would fit your structure):
- Allow combining multiple allowed cases
- No glob patterns required
- Keep the flexibility to override rule... | 2020-03-17T14:38:18 | 2020-03-17T14:39:30 | {} | CONTRIBUTOR |
vuejs | core | 600,769,168 | 827 | beardedvikingdev | Hi, I'd like to pick this up if it's available :) | 2020-03-18T17:39:49 | 2020-03-18T17:39:49 | {} | NONE |
vuejs | core | 595,190,551 | 799 | LinusBorg | Related code:
https://github.com/vuejs/vue-next/blob/fb4856b36375fcf3eecaf89f260b272052a0b432/packages/reactivity/src/collectionHandlers.ts#L75-L87
The cause of this bug is that we assume that the raw Map / Set contains no proxies, and instead only contains raww values.
So we probably have to check for both th... | 2020-03-05T11:50:30 | 2020-03-05T11:50:30 | {} | MEMBER |
vuejs | core | 595,915,142 | 805 | yyx990803 | Should be fixed by https://github.com/vuejs/vue-next/pull/801? | 2020-03-06T19:07:18 | 2020-03-06T19:07:18 | {} | MEMBER |
vuejs | core | 595,945,267 | 805 | DanielRosenwasser | Yup! Sorry, didn't know @sandersn was on it. | 2020-03-06T20:09:51 | 2020-03-06T20:10:24 | {} | CONTRIBUTOR |
vuejs | core | 597,884,241 | 815 | jbruni | Thanks, @yyx990803
What would be the recommended approach for adding a `draggable` behaviour which could be attached to any component?
For the consumer perspective:
- a wrapper component, like `<draggable><consumer-something /></draggable>` ?
- a custom directive, like `<consumer-something v-draggable />` ?
... | 2020-03-11T21:20:50 | 2020-03-11T21:25:59 | {} | NONE |
vuejs | core | 599,047,229 | 832 | jiangying000 | Because browser parsed the template in a different way from vue-template-compiler, so innerHTML inside `#app` has already changed before consumed by Vue.
Three ways to resolve this issue:
1. rewrite
```html
<Hello name=A v-if=toggle />
<Hello name=B v-else />
```
to
```html
<Hel... | 2020-03-14T11:54:11 | 2020-03-14T11:55:10 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.