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 | 681,052,634 | 1,977 | yyx990803 | Wait for the next release of the eslint plugin. You can disable the lint rule for now. | 2020-08-26T18:35:59 | 2020-08-26T18:35:59 | {} | MEMBER |
vuejs | core | 679,472,121 | 1,945 | cool-little-fish | Em... I think if it's a root node update, then there will be no next,
so it will never get into updateComponentPreRender function. | 2020-08-25T02:54:37 | 2020-08-25T02:55:20 | {} | CONTRIBUTOR |
vuejs | core | 680,456,392 | 1,762 | troy351 | Chrome 85 just released and it seems this bug was gone. | 2020-08-26T02:57:43 | 2020-08-26T02:57:43 | {} | NONE |
vuejs | core | 680,918,822 | 1,971 | yyx990803 | You were never able to get component instances from slot functions. Slots have always been vnodes.
If you want to filter slot vnodes, do it using a render function instead of template.
Also - this is a vague and generic question and should not be posted as an issue. | 2020-08-26T14:34:21 | 2020-08-26T14:34:55 | {} | MEMBER |
vuejs | core | 680,960,061 | 1,888 | yyx990803 | I left the comment in #1850 thinking we did not already have a warning for this, but turns out we already do. I think the current one is good enough. | 2020-08-26T15:42:03 | 2020-08-26T15:42:03 | {} | MEMBER |
vuejs | core | 681,020,263 | 1,976 | meteorlxy | BTW, consider bumping prettier to 2.1.0+ ?
It would have better support for typescript 4.0.0:
https://prettier.io/blog/2020/08/24/2.1.0.html#typescript
Current version of prettier even does not support `import type { } from ...` and `export type { }` syntax
---
Two breaking changes:
- the `trailingCom... | 2020-08-26T17:30:56 | 2020-08-26T17:48:31 | {} | MEMBER |
vuejs | core | 681,076,140 | 1,976 | yyx990803 | Prettier is pinned because of the nested ternary formatting. I'll probably only considering bumping if there are new TS syntax that cannot be handled. | 2020-08-26T19:22:57 | 2020-08-26T19:22:57 | {} | MEMBER |
vuejs | core | 682,475,360 | 1,991 | posva | Cannot reproduce but I see the warning you are talking about. You cannot use any code that would rely on enumerating the keys of a component instance (`getCurrentInstance`) like `Obeject.keys` or other functions.
I tried searching where it comes from but I couldn't find it in your code. | 2020-08-28T11:31:17 | 2020-08-28T11:31:17 | {} | MEMBER |
vuejs | core | 682,452,933 | 1,995 | Fuzzyma | > Just use [`<foreignObject>`](https://developer.mozilla.org/en-US/docs/Web/SVG/Element/foreignObject) to wrap the `Teleport` component.
I just wanted to answer that this is exactly what I proposed in the issue of vue-portal but I just realized its actually far better.
So this would be:
```svg
<svg>
...
<... | 2020-08-28T10:31:27 | 2020-08-28T10:54:06 | {} | NONE |
vuejs | core | 682,612,016 | 1,991 | mon-compte-github | > I tried searching where it comes from but I couldn't find it in your code.
I didn't either ¯\\\_(ツ)\_/¯ that's why i opened this ticket . Thanks for your reply anyway. | 2020-08-28T14:25:00 | 2020-08-28T14:25:53 | {} | NONE |
vuejs | core | 682,896,417 | 1,995 | yyx990803 | Closing since `<foreignObject>` works. Auto switching namespace isn't optimal since it means destroying and re-creating all the nodes. | 2020-08-28T16:59:07 | 2020-08-28T16:59:07 | {} | MEMBER |
vuejs | core | 679,393,905 | 1,945 | yyx990803 | Thanks for the PR! It is possible for `optimized` to be false here if the component happens to be the root node (which means it doesn't have a parent block to enter optimized mode), but still it *can* have a positive patchFlag.
See 499bc0bf | 2020-08-24T22:15:18 | 2020-08-24T22:15:18 | {} | MEMBER |
vuejs | core | 679,450,421 | 1,953 | yyx990803 | The merging behavior is rarely used and IMO it'd be better to stop supporting it, since it leads really implicit coupling that is hard to reason about. Will draft an RFC. | 2020-08-25T01:33:37 | 2020-08-25T01:33:37 | {} | MEMBER |
vuejs | core | 680,802,506 | 1,970 | posva | > I don't quite understand how I would simply "create a copy" (with more complex objects like a Map).
You cannot pass a Map to HistoryState, you will have to serialize it yourself anyway
> If Proxies just can't be made to work with the SCA, then I think Vue should provide a deep variant of toRaw. Otherwise, as fa... | 2020-08-26T10:41:41 | 2020-08-26T10:41:41 | {} | MEMBER |
vuejs | core | 680,885,783 | 1,378 | Kadeluxe | Issue happens if you suddenly have `"declaration": true` in your TypeScript config.
Spent a couple of hours trying to identify and reproduce this issue in my project (I don't use vue-cli). | 2020-08-26T13:39:12 | 2020-08-26T13:39:12 | {
"+1": 5
} | NONE |
vuejs | core | 680,959,361 | 1,972 | yyx990803 | Calling twice on reactive keys is necessary for the desired behavior. Wouldn't really say it's a bug. | 2020-08-26T15:40:52 | 2020-08-26T15:40:52 | {} | MEMBER |
vuejs | core | 682,201,099 | 1,994 | jacekkarczmarczyk | 
| 2020-08-27T21:30:23 | 2020-08-27T21:30:23 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 682,379,300 | 1,997 | HcySunYang | You can also return `null` directly | 2020-08-28T07:40:46 | 2020-08-28T07:40:46 | {} | MEMBER |
vuejs | core | 682,402,111 | 1,997 | dxvladislavvolkov | @HcySunYang yes. It works. Thanks!
But why do I get the warning with h function? | 2020-08-28T08:35:10 | 2020-08-28T08:35:10 | {} | NONE |
vuejs | core | 682,420,177 | 1,228 | spikyjt | For completeness, it's worth pointing out that `skipLibCheck` will skip checking any declaration files in your own project, which may not be what you want, e.g. if you have the habit of declaring purely ambient entities (e.g. types, interfaces) in `.d.ts` files. There's no need to do this in a project that is built to ... | 2020-08-28T09:13:02 | 2020-08-28T09:14:57 | {} | NONE |
vuejs | core | 678,953,082 | 1,947 | peng | I think you write a wrong way. | 2020-08-24T07:17:19 | 2020-08-24T07:17:19 | {} | NONE |
vuejs | core | 679,114,158 | 1,947 | HcySunYang | I tracked the issue and this test case can reproduce it:
```js
test('flushPostFlushCbs', async () => {
let count = 0
const mounted1 = () => {
renderJob(mounted2)
}
const mounted2 = () => {
count++
}
const renderJob = (hook: Function) => {
queuePostFlushCb(hook)
... | 2020-08-24T13:05:41 | 2020-08-24T13:08:06 | {} | MEMBER |
vuejs | core | 679,378,129 | 1,946 | CyberAP | You can use a factory pattern for this:
```js
const createSetModel = name => ({
get() { return Array.from(this[name]) },
set(value) { this[name] = new Set(value) }
})
export default {
data() {
return {
value: new Set()
}
},
computed: {
model: createSetModel('value')
}
}
`... | 2020-08-24T21:33:38 | 2020-08-24T21:33:38 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 679,407,600 | 1,937 | dsonet | Why not just compare the 2 values? The less involved the better performance. | 2020-08-24T22:58:10 | 2020-08-24T22:58:10 | {} | CONTRIBUTOR |
vuejs | core | 679,450,985 | 1,955 | yyx990803 | Sorry, didn't see this and I already removed it in 59e58cd4 | 2020-08-25T01:35:47 | 2020-08-25T01:35:47 | {} | MEMBER |
vuejs | core | 680,884,414 | 1,960 | yyx990803 | Cool, I'm closing this for now since there's no direct actions to take, but this is an interesting exploration and will likely help us when we work on IE11 compat in core. | 2020-08-26T13:36:43 | 2020-08-26T13:36:43 | {
"+1": 2
} | MEMBER |
vuejs | core | 680,927,615 | 1,970 | yyx990803 | Technically `deepToRaw` is not possible, because in the example of
```js
const s = reactive({
foo: reactive({})
})
```
The raw version of `s` does contain `foo` as a reactive object. If you want `s.foo` to be a raw object as well, you must clone raw `s` - but that is no longer the actual raw `s`. Which mean... | 2020-08-26T14:48:20 | 2020-08-26T14:48:47 | {
"+1": 2
} | MEMBER |
vuejs | core | 681,792,901 | 1,983 | cool-little-fish | The 34fde9267ecc18eef4805881305a30267d2da1d2 is better, because it contains the mutilple extend & mixin. | 2020-08-27T08:38:04 | 2020-08-27T08:38:04 | {} | CONTRIBUTOR |
vuejs | core | 679,338,191 | 1,933 | yyx990803 | Yeah this doesn't feel quite right - it essentially disables all the method argument inference. | 2020-08-24T20:05:16 | 2020-08-24T20:05:16 | {} | MEMBER |
vuejs | core | 680,335,376 | 1,166 | sagalbot | It's worth noting that the current v3 docs do explicitly note support for `v-for` with `refs`:
> When ref is used together with v-for, the ref you get will be an array containing the child components mirroring the data source.
https://v3.vuejs.org/guide/component-template-refs.html
If this should be changed to... | 2020-08-26T00:12:16 | 2020-08-26T00:12:16 | {} | NONE |
vuejs | core | 680,850,483 | 1,970 | yagebu | > Just use toRaw():
I tried that, it only seems be a shallow `toRaw`: https://codesandbox.io/s/distracted-keldysh-00h8c
A `deepToRaw` would be a good fix/workaround IMHO :) (or probably for consistency, `toRaw` and `shallowToRaw`) | 2020-08-26T12:32:28 | 2020-08-26T12:32:28 | {} | NONE |
vuejs | core | 682,304,689 | 1,995 | HcySunYang | Just use [`<foreignObject>`](https://developer.mozilla.org/en-US/docs/Web/SVG/Element/foreignObject) to wrap the `Teleport` component. | 2020-08-28T03:28:07 | 2020-08-28T03:28:07 | {} | MEMBER |
vuejs | core | 682,762,795 | 2,003 | yaadata | If this is a documentation issue, I feel it's best for you to report at [docs-next](https://github.com/vuejs/docs-next) because that's the repo that deals with the migration guide | 2020-08-28T15:54:53 | 2020-08-28T15:54:53 | {} | NONE |
vuejs | core | 682,853,154 | 1,958 | yyx990803 | This is likely a wontfix since I don't see the benefit being worth it. | 2020-08-28T16:39:46 | 2020-08-28T16:39:46 | {} | MEMBER |
vuejs | core | 678,800,064 | 1,679 | skirtles-code | @advanderveer I believe you need to put the setting on the component rather than the application:
```js
Vue.createApp({
delimiters: ['{%', '%}']
})
``` | 2020-08-23T17:15:08 | 2020-08-23T17:15:08 | {} | CONTRIBUTOR |
vuejs | core | 678,943,038 | 1,931 | peng | @bhaidar Can you show a full example. I saw no select in your example code. Fetch data have cors problem. Use fake data replace | 2020-08-24T06:55:51 | 2020-08-24T06:55:51 | {} | NONE |
vuejs | core | 678,995,343 | 1,931 | skirtles-code | @peng It seems the CodeSandbox example has been changed since it was first posted.
Here's an example of the same problem:
https://jsfiddle.net/skirtle/24jk3roL/ | 2020-08-24T08:46:13 | 2020-08-24T08:46:13 | {} | CONTRIBUTOR |
vuejs | core | 681,926,372 | 1,989 | leopiccionia | If I append an empty `<span/>` to `component-a` template, making it a Fragment, it works as expected. So it's possible that the problem is an over-optimization. | 2020-08-27T12:46:35 | 2020-08-27T12:46:35 | {} | CONTRIBUTOR |
vuejs | core | 682,838,443 | 1,997 | yyx990803 | `h` does not accept `null`. Also don't use `createCommentVNode`, that's internal.
Just `return null`. | 2020-08-28T16:30:53 | 2020-08-28T16:30:53 | {
"+1": 3
} | MEMBER |
vuejs | core | 613,692,666 | 910 | yyx990803 | https://github.com/vuejs/vue-next/commit/78977c399734da7c4f8d58f2ccd650533e89249f | 2020-04-14T21:33:40 | 2020-04-14T21:33:40 | {} | MEMBER |
vuejs | core | 614,705,790 | 970 | yyx990803 | This has been experimented in the past, and the general conclusion is that communication overhead between the main thread and the worker thread plus the increased architectural complexity outweighs the performance gains. | 2020-04-16T14:57:27 | 2020-04-16T14:57:27 | {} | MEMBER |
vuejs | core | 615,004,992 | 974 | 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-04-17T02:35:01 | 2020-04-17T02:35:01 | {} | CONTRIBUTOR |
vuejs | core | 615,151,299 | 972 | posva | This should be fixed in the latest vue-router release | 2020-04-17T09:43:34 | 2020-04-17T09:43:34 | {
"+1": 1
} | MEMBER |
vuejs | core | 616,728,323 | 994 | jods4 | @yyx990803 I feel like you dismissed this issue a bit quickly, without providing guidance for something that is more legitimate than you make it sound.
If `unmounted` is linked to the vnode lifecycle by design that's fine, then maybe we need another event that's linked to the DOM removal?
Or maybe just change whe... | 2020-04-20T18:20:52 | 2020-04-20T18:20:52 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 617,625,121 | 1,019 | yyx990803 | 1. Class has more issues than it solves https://composition-api.vuejs.org/#type-issues-with-class-api
2. Vue doesn't need to use Class API to get type hints. Vetur has had intellisense support for templates for a very long time by analyzing the object syntax, just not performing actual type checking. @znck has made ... | 2020-04-22T08:14:26 | 2020-04-22T08:14:26 | {} | MEMBER |
vuejs | core | 617,626,095 | 1,020 | yyx990803 | Read the RFCs before opening issues please. | 2020-04-22T08:16:25 | 2020-04-22T08:16:25 | {} | MEMBER |
vuejs | core | 614,082,803 | 834 | yyx990803 | Closing per discussion in https://github.com/vuejs/rfcs/issues/157 | 2020-04-15T14:44:47 | 2020-04-15T14:44:47 | {} | MEMBER |
vuejs | core | 614,108,164 | 579 | yyx990803 | Sorry for the accidental merge, can you open a follow up PR for the type test fix please? | 2020-04-15T15:28:01 | 2020-04-15T15:28:01 | {
"+1": 1
} | MEMBER |
vuejs | core | 615,011,927 | 975 | 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-04-17T03:03:36 | 2020-04-17T03:03:36 | {} | CONTRIBUTOR |
vuejs | core | 616,013,820 | 990 | ghost | > Hope [vuejs/vue-next-webpack-preview#5](https://github.com/vuejs/vue-next-webpack-preview/issues/5) can help you.
Hello, Has Vue3 Doc translation started? Is there any way to join? Thank you very much | 2020-04-19T02:52:27 | 2020-04-19T02:52:27 | {
"eyes": 1
} | NONE |
vuejs | core | 616,025,653 | 990 | mannok | > Hope [vuejs/vue-next-webpack-preview#5](https://github.com/vuejs/vue-next-webpack-preview/issues/5) can help you.
Thanks! That help solves... | 2020-04-19T04:18:33 | 2020-04-19T04:18:33 | {} | NONE |
vuejs | core | 617,963,744 | 1,026 | yyx990803 | This is also fixed by 7d0ab339 | 2020-04-22T18:49:45 | 2020-04-22T18:49:45 | {} | MEMBER |
vuejs | core | 614,144,952 | 963 | pikax | I doubt we can do anything with our types, the problem can be boil down to
```ts
function f<T>(a: T): T {
return {} as any
}
function c<T>(d: () => T): T {
return {} as any
}
const x = f({
a: 1,
ff: c(() => {
return x.a;
})
})
```
[typescript playground](https://www.typescriptlang.org/pl... | 2020-04-15T16:32:51 | 2020-04-15T16:32:51 | {} | MEMBER |
vuejs | core | 614,532,545 | 968 | cexbrayat | It builds with `@types/node` up until v12, but it doesn't with v13. But the main issue is that an app using vue alpha.13 now has to add `node` in its tsconfig.json otherwise it does not compile. | 2020-04-16T09:33:47 | 2020-04-16T09:33:47 | {} | MEMBER |
vuejs | core | 615,030,487 | 973 | Jesonhu | https://vue-composition-api-rfc.netlify.app/api.html It may be useful | 2020-04-17T04:11:38 | 2020-04-17T04:11:38 | {} | NONE |
vuejs | core | 615,054,030 | 977 | kiaking | Your example works in that use case, and you are free to implement your code like that. However, that will probably wouldn't work on SSR in the real-world use case, and it will also not work outside of `setup` hook, so you can't use it with the option syntax component.
Vuex is there to support global state managemen... | 2020-04-17T05:41:53 | 2020-04-17T05:41:53 | {
"+1": 11
} | MEMBER |
vuejs | core | 616,699,095 | 1,003 | yyx990803 | There is continuous coverage tracking at https://vue-next-coverage.netlify.app/
We will likely dedicate a period before final release to improve coverage, but as of now it's not a top priority. | 2020-04-20T17:24:41 | 2020-04-20T17:24:41 | {} | MEMBER |
vuejs | core | 617,628,442 | 1,020 | LemonAppleMo | > Read the RFCs before opening issues please.
不好意思，我下次会先看RFCs。 | 2020-04-22T08:21:11 | 2020-04-22T08:21:11 | {} | NONE |
vuejs | core | 617,846,819 | 1,030 | underfin | The fallback will be include into dynamicChildren with slotOutlet in runtime.so, should let it into wrapper funtion in compiler time. | 2020-04-22T15:23:22 | 2020-04-22T15:23:22 | {} | MEMBER |
vuejs | core | 617,963,498 | 1,015 | yyx990803 | This is also fixed by 7d0ab339 | 2020-04-22T18:49:17 | 2020-04-22T18:49:17 | {} | MEMBER |
vuejs | core | 612,192,627 | 579 | pikax | @yyx990803 is this useful or just close it? | 2020-04-10T19:57:27 | 2020-04-10T19:57:27 | {} | MEMBER |
vuejs | core | 612,583,334 | 951 | jacekkarczmarczyk | see also
```ts
interface Foo1 { [Symbol.iterator]: any }
interface Foo2 { }
const foo1: Ref<Foo1|null> = ref<Foo1|null>(null);
const foo2: Ref<Foo2|null> = ref<Foo2|null>(null);
console.log(foo1, foo2);
``` | 2020-04-12T08:45:19 | 2020-04-12T08:45:19 | {} | CONTRIBUTOR |
vuejs | core | 613,392,681 | 961 | CyberAP | Why? | 2020-04-14T11:43:46 | 2020-04-14T11:43:46 | {} | CONTRIBUTOR |
vuejs | core | 615,047,862 | 973 | Justineo | Our docs team is working on it. We'll announce it when it's fully prepared. Thanks! | 2020-04-17T05:18:05 | 2020-04-17T05:18:16 | {
"+1": 2
} | MEMBER |
vuejs | core | 616,090,732 | 991 | himself65 | Still work in progress, comment is welcome | 2020-04-19T09:53:04 | 2020-04-19T11:31:49 | {} | CONTRIBUTOR |
vuejs | core | 616,706,532 | 994 | yyx990803 | This is expected behavior and is also consistent with Vue 2's behavior. The element is considered unmounted the moment the leave transition starts (or, the leave transition is triggered by the unmount of the element). This conceptually aligns with the fact that once the leave transition starts, the content is considere... | 2020-04-20T17:38:27 | 2020-04-20T17:38:40 | {} | MEMBER |
vuejs | core | 616,776,207 | 987 | yyx990803 | I don't think we should expose the exception - this would cause any error in the error handler to crash the app, which defeats the purpose of having an error handler. | 2020-04-20T19:58:27 | 2020-04-20T19:58:27 | {} | MEMBER |
vuejs | core | 616,789,407 | 994 | yyx990803 | In this case, I don't understand why Popper.js removes the styling on cleanup. Why can't it only remove the listeners?
What I mean by unfortunate is that Popper.js' cleanup contains both interaction cleanup and visual updates that cannot be separated.
Conceptually in Vue, an `unmounted` element is forever discard... | 2020-04-20T20:26:32 | 2020-04-20T20:32:24 | {} | MEMBER |
vuejs | core | 614,107,605 | 579 | yyx990803 | Oops, looks like I hit the button at the wrong time | 2020-04-15T15:27:03 | 2020-04-15T15:27:03 | {} | MEMBER |
vuejs | core | 615,149,911 | 972 | zce | @zhuyankun
Here are some helpful links for you.
- https://github.com/vuejs/vue-next/commit/09b4202a22ae03072a8a8405511e37f65b626568
- https://github.com/vuejs/vue-router-next/commit/7636f556cd654fbdf49b494925628593e8383453 | 2020-04-17T09:40:33 | 2020-04-17T09:40:33 | {} | NONE |
vuejs | core | 615,169,009 | 794 | posva | Thanks for the PR but apparently this was already fixed.
See https://github.com/vuejs/vue-next/issues/681#issuecomment-615167018 | 2020-04-17T10:23:21 | 2020-04-17T10:23:21 | {} | MEMBER |
vuejs | core | 615,237,167 | 982 | yyx990803 | I manually squashed and force pushed ¯\_(ツ)_/¯ | 2020-04-17T13:14:02 | 2020-04-17T13:14:02 | {} | MEMBER |
vuejs | core | 615,932,160 | 989 | rigor789 | @posva looks like it's being used in `runtime-dom`:
https://github.com/vuejs/vue-next/blob/9e48c51f0707bc881304e592d52aedc5faa20526/packages/runtime-dom/src/modules/style.ts#L29
There are a few more places, but they are mostly in compiler, so less of a concern:
https://github.com/vuejs/vue-next/search?q=startsW... | 2020-04-18T19:29:02 | 2020-04-18T19:29:02 | {} | CONTRIBUTOR |
vuejs | core | 616,807,026 | 987 | pikax | > My point is in your test setup you don't need the `errorHandler` at all - then it will just throw as expected.
It only throws during production, because I'm running my tests in `__DEV__`, is not throwing. Although `runtime-core.cjs.js` doesn't even have the branch to throw exception
---
The way I'm doing in ... | 2020-04-20T21:02:00 | 2020-04-20T21:02:00 | {} | MEMBER |
vuejs | core | 617,133,791 | 1,013 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/963 | 2020-04-21T11:54:48 | 2020-04-21T11:54:48 | {
"+1": 1
} | MEMBER |
vuejs | core | 614,097,952 | 964 | sionzee | Additional Comment
Even when `shallowRef` is not making value reactive, what should be the proper way to update array of components?
In the reproduction case there is structure with `comp` and `id`. That makes sense why it is not updated. (realized after opening the issue) But if we cannot use `ref` on component... | 2020-04-15T15:10:38 | 2020-04-15T15:11:25 | {} | NONE |
vuejs | core | 614,528,434 | 968 | pikax | Can you provide a repo to reproduce this?
I tested with node `v10.13.0`, but was able to build without any issues
| 2020-04-16T09:25:50 | 2020-04-16T09:25:50 | {} | MEMBER |
vuejs | core | 614,954,755 | 971 | dsonet | Your reproduction link doesn't work, can't even compile | 2020-04-16T23:49:48 | 2020-04-16T23:49:48 | {} | CONTRIBUTOR |
vuejs | core | 616,781,122 | 987 | pikax | The reason is to expose the place where the exception happen, not exposing the exception will make the test pass but to log the exception.
```ts
import { createApp } from "vue";
describe("test", () => {
it("test", () => {
createApp({
setup() {
expect(1).toBe(2);
},
}).mount(do... | 2020-04-20T20:08:57 | 2020-04-20T20:08:57 | {} | MEMBER |
vuejs | core | 612,593,021 | 951 | LinusBorg | (Sorry for the close, mouse finger messed up ^^)
We can easily fix the problem with `HTMLElement` and similar Types (`Window`, `Document`) by adding them to the `BaseTypes`. That's correct as the properties of these types shouldn't be recursively walked by `Unwrap` anyways. I'll have a PR up for that in a second.
... | 2020-04-12T10:18:54 | 2020-04-13T15:54:58 | {} | MEMBER |
vuejs | core | 613,097,539 | 910 | jods4 | @yyx990803 Got it.
It was hard but I managed to nail down a small repro.
https://jsfiddle.net/e635agws/15/
Click on the button with the dev tools open, you'll see that `some.name` is evaluated with `some` being null, even though that binding is inside a `v-if="some"`. | 2020-04-13T21:04:52 | 2020-04-13T21:04:52 | {} | CONTRIBUTOR |
vuejs | core | 613,705,915 | 962 | yyx990803 | See the commit - in your case, it's recommended to use `shallowRef` instead (which doesn't make its value reactive) | 2020-04-14T22:08:30 | 2020-04-14T22:08:30 | {} | MEMBER |
vuejs | core | 614,100,280 | 964 | yyx990803 | A `shallowRef` only tracks mutation of its own `.value` property. Mutating the array inside won't be reactive. If you want to track the mutation of the array you should be using `shallowReactive([])` | 2020-04-15T15:14:45 | 2020-04-15T15:14:45 | {} | MEMBER |
vuejs | core | 614,655,701 | 968 | yyx990803 | We should remove it anyway since it's only Stage 1. | 2020-04-16T13:33:26 | 2020-04-16T13:33:26 | {} | MEMBER |
vuejs | core | 616,126,089 | 992 | yyx990803 | The target element cannot be a part of the same component... It needs to be outside of `<div id="app">`. | 2020-04-19T12:47:47 | 2020-04-19T14:49:28 | {
"+1": 3,
"-1": 24,
"confused": 25
} | MEMBER |
vuejs | core | 616,923,188 | 1,006 | 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-04-21T03:02:37 | 2020-04-21T03:02:37 | {} | CONTRIBUTOR |
vuejs | core | 617,132,835 | 1,013 | 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-04-21T11:52:35 | 2020-04-21T11:52:35 | {} | CONTRIBUTOR |
vuejs | core | 617,133,602 | 1,014 | 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-04-21T11:54:23 | 2020-04-21T11:54:23 | {} | CONTRIBUTOR |
vuejs | core | 614,109,258 | 579 | pikax | Sorry about that, should have run the testing before pushing | 2020-04-15T15:29:49 | 2020-04-15T15:29:49 | {} | MEMBER |
vuejs | core | 614,135,323 | 965 | yyx990803 | 🎉 | 2020-04-15T16:15:26 | 2020-04-15T16:15:26 | {} | MEMBER |
vuejs | core | 615,046,091 | 973 | masx200 | > https://vue-composition-api-rfc.netlify.app/api.html It may be useful
But there are many other contents included in vue3, which is obviously incomplete. | 2020-04-17T05:12:13 | 2020-04-17T05:12:13 | {} | NONE |
vuejs | core | 615,168,557 | 681 | posva | This seems to be fixed in the latest release | 2020-04-17T10:22:19 | 2020-04-17T10:22:19 | {} | MEMBER |
vuejs | core | 615,928,274 | 989 | rigor789 | I'm always a little skeptical with perf tests - both of our benchmarks can go either way between runs. But for the most common strings, it does seem like `startsWith` is indeed faster! | 2020-04-18T19:06:21 | 2020-04-18T19:06:21 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 616,012,648 | 990 | underfin | Hope https://github.com/vuejs/vue-next-webpack-preview/issues/5 can help you. | 2020-04-19T02:43:48 | 2020-04-19T02:43:48 | {
"+1": 5
} | MEMBER |
vuejs | core | 617,592,676 | 1,020 | posva | It's `onClick` now instead of a nested object. See https://github.com/vuejs/rfcs/blob/master/active-rfcs/0008-render-function-api-change.md | 2020-04-22T07:05:29 | 2020-04-22T07:05:29 | {} | MEMBER |
vuejs | core | 612,608,474 | 952 | rigor789 | I wonder if this could be done in the `runtime-dom` package to avoid adding DOM dependencies (even if they are just in the types) to the `reactivity` package?
This would allow custom renderers to make the same adjustments with `HostElement` and other as needed. | 2020-04-12T12:42:21 | 2020-04-12T12:42:21 | {} | CONTRIBUTOR |
vuejs | core | 616,924,186 | 991 | himself65 | right. Closing this pr | 2020-04-21T03:06:21 | 2020-04-21T03:06:21 | {} | CONTRIBUTOR |
vuejs | core | 617,754,151 | 1,019 | leopiccionia | The lack of `v-on` and `$emit` type-checking is not related to class v object. Vue 2.x just doesn't have a way to type-check emits, so far.
But Vue 3.x introduced the new [`emits` option](https://github.com/vuejs/rfcs/blob/master/active-rfcs/0030-emits-option.md) to solve this problem, and new class components will ... | 2020-04-22T12:39:24 | 2020-04-22T12:39:24 | {} | CONTRIBUTOR |
vuejs | core | 615,128,889 | 982 | posva | There seems to be an unrelated test failing (I only changed typings) | 2020-04-17T08:55:01 | 2020-04-17T08:55:01 | {} | MEMBER |
vuejs | core | 615,235,144 | 978 | yyx990803 | Thanks for the PR, but the `node.type` is a necessary type guard to ensure the node has a `.name` property. As for the loc part, it's called only when there are errors so it's not perf critical. | 2020-04-17T13:09:51 | 2020-04-17T13:09:51 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.