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 | 977,787,471 | 4,988 | unbyte | We have two behaviors of watch that have not yet been documented (in official documentation):
- watching deeply will be applied automatically when a watch source is reactive, and
- watching deeply will trace all reactives/refs in the substructure of the watch source.
This PR breaks the second one, but this is mo... | 2021-11-24T11:26:37 | 2021-11-24T11:26:37 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 977,984,075 | 4,991 | posva | This happens because the `this` in `this.addMessage()` inside of `constructor()` of Parent is not the reactive proxy created with `ref()` and thus doesn't trigger anything. You need to ensure the `this` is the `parent.value`, the reactive proxy [like this for example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBz... | 2021-11-24T15:28:44 | 2021-11-24T15:28:44 | {
"hooray": 2
} | MEMBER |
vuejs | core | 979,469,525 | 4,807 | JensDll | This does break one of the type tests in `ref.test-d.ts` btw (looks like no actions were run for this one).
https://github.com/vuejs/vue-next/blob/4e1131e251c1e3c9278853b41a3458a71e702959/test-dts/ref.test-d.ts#L46
With the current change, tuple refs like `[number, string]` get widened to `(string | number)[]`.
[T... | 2021-11-25T21:08:20 | 2021-11-25T21:08:20 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 980,501,046 | 5,006 | mehanalavimajd | > Could you give some introduction about this commit?
This PR will add more html entities(like ©) to the htmlescape.ts for better escaping. I just saw that there are only 4 entites so I made this PR . If you don't need them tell me to close the PR | 2021-11-27T04:39:25 | 2021-11-27T04:39:25 | {} | CONTRIBUTOR |
vuejs | core | 981,113,448 | 5,013 | posva | You can read about how to handle this at https://v3.vuejs.org/guide/component-custom-events.html#multiple-v-model-bindings. You might also want to lookup `inheritAttrs` for custom form elements.
---
Please, next time consider using the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org... | 2021-11-28T16:27:46 | 2021-11-28T18:25:14 | {} | MEMBER |
vuejs | core | 977,197,938 | 4,950 | kadiryazici | @yuwu9145 Why not working for mine :D 🤔 What version are you using? | 2021-11-23T21:49:30 | 2021-11-23T21:49:44 | {} | CONTRIBUTOR |
vuejs | core | 979,066,253 | 4,873 | yyx990803 | I also think copying any existing self properties would be safer - the assumption that "a function with extra properties doesn't need access to `this`" seems pretty fragile to me.
Copying with `Object.assign` should be acceptable since in most cases the function will have no extra properties, and the code path only ... | 2021-11-25T10:22:18 | 2021-11-25T10:22:18 | {} | MEMBER |
vuejs | core | 981,417,783 | 5,014 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js).
maybe you are looking for this: https://v3.vuejs.org/gu... | 2021-11-29T09:01:04 | 2021-11-29T09:01:49 | {} | MEMBER |
vuejs | core | 982,251,266 | 5,018 | yangliguo7 | the code like：
```html
< template >
< button v-operate:add >button< /button >
< /template >
<script setup>
const add = () =>{
console.log('click trigger')
}
</script>
```
```js
app.directive("operate", {
mounted(el, binding) {
const { arg, instance, value } = binding;
c... | 2021-11-30T03:30:30 | 2021-11-30T07:18:22 | {} | CONTRIBUTOR |
vuejs | core | 975,217,846 | 4,975 | yyx990803 | What's the purpose of getting the `v-pre` tag?
Note that `v-pre` is a special directive that affects AST shape in that inside an element with `v-pre`:
1. Mustaches are ignored and treated as plain text
2. Directives inside `v-pre` are parsed as plain attributes
This is similar to how you won't find `v-if` or ... | 2021-11-22T07:57:14 | 2021-11-22T07:57:14 | {} | MEMBER |
vuejs | core | 979,052,524 | 4,964 | cexbrayat | This was spotted in VTU, as props are rendered as attributes when using shallow mount. We can work around it in VTU, but I was wondering if the cleanest way was not to fix it in core. | 2021-11-25T10:04:23 | 2021-11-25T10:04:23 | {} | MEMBER |
vuejs | core | 979,434,634 | 4,933 | rashfael | This is probably related:
When using `mode="in-out"` instead in the reproduction and navigating from next2 to next, the content of next2 does not disappear. | 2021-11-25T19:22:33 | 2021-11-25T19:22:33 | {} | NONE |
vuejs | core | 979,771,656 | 4,873 | LinusBorg | Done | 2021-11-26T08:11:36 | 2021-11-26T08:11:36 | {} | MEMBER |
vuejs | core | 980,477,689 | 4,987 | ygj6 | > Can it also fix #4999 ?It seems i did repeated work...
Sorry, it's my fault, this PR can't fix #4999:cold_sweat: | 2021-11-27T00:49:10 | 2021-11-27T00:49:10 | {
"+1": 1
} | MEMBER |
vuejs | core | 981,577,460 | 5,008 | ygj6 | > 4.npm install
Maybe you could skip this step, so that the `vue` of the sub-component and the main component `import` point to the same place. It seems like not vue's bug. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackove... | 2021-11-29T12:12:18 | 2021-11-29T12:12:18 | {} | MEMBER |
vuejs | core | 979,439,619 | 4,998 | posva | I would say this is expected because that's how HTML attributes and are not adapted like props are when it comes to their naming. Also, this would be a breaking change | 2021-11-25T19:36:53 | 2021-11-25T19:36:53 | {} | MEMBER |
vuejs | core | 979,759,373 | 4,989 | ThaDaVos | Ah, it didn't look to be a duplicate as it was about importing the type from an external file - while I am defining the interface inside the same file and extending a type from a external file | 2021-11-26T07:49:07 | 2021-11-26T07:49:07 | {
"+1": 1
} | NONE |
vuejs | core | 979,805,423 | 5,001 | mazg1987 | i have solved this question by install vetur plugin in vscode。
thanks | 2021-11-26T09:07:55 | 2021-11-26T09:07:55 | {
"+1": 2
} | NONE |
vuejs | core | 980,443,607 | 4,960 | mrts | Yes, my original proposal is too radical. Nevertheless, I think we should provide a reasoned recommendation for the common "fetch data from a REST API, show a spinner while the request executes and display the result in the component when it is done" case. There are too many options at the moment which is confusing.
... | 2021-11-26T21:36:27 | 2021-11-26T21:37:11 | {
"+1": 7
} | NONE |
vuejs | core | 982,315,640 | 5,019 | snowwolfjay | 你可以用vshow, 被删除的元素不会被包含的 | 2021-11-30T06:05:15 | 2021-11-30T06:05:15 | {} | NONE |
vuejs | core | 977,424,435 | 4,984 | edison1105 | @lejianwen 这应该是个 bug，还没来得及调查，后面会修复的。
this should be a bug, beacuse `tab1.vue` is unmounted.
| 2021-11-24T02:30:01 | 2021-11-24T02:30:01 | {
"+1": 3
} | MEMBER |
vuejs | core | 978,796,100 | 4,994 | yyx990803 | Please provide a reproduction as required by the issue guidelines.
> "Simply have a defineProps inside a script setup. Fails at runtime."
This doesn't help because obviously it's not happening to other users. It's related to your build setup and without that information there's nothing we can do. | 2021-11-25T03:36:52 | 2021-11-25T03:37:58 | {} | MEMBER |
vuejs | core | 978,911,418 | 4,995 | LinusBorg | 1. This reproduction is a whole template - we need a minimal reproduction focused on the actual problem.
2. It seems you try to transition to a component that renders multiple root nodes - that's not possible, as the error message states. | 2021-11-25T07:35:58 | 2021-11-25T07:36:08 | {} | MEMBER |
vuejs | core | 979,583,893 | 4,873 | caozhong1996 | It seems caused by #4807🤔 | 2021-11-26T01:22:49 | 2021-11-26T01:22:49 | {} | CONTRIBUTOR |
vuejs | core | 979,657,329 | 4,836 | yyx990803 | Thanks for the great effort! It will probably take me some time to go over all of them but looking good so far. | 2021-11-26T03:17:19 | 2021-11-26T03:17:19 | {
"hooray": 1
} | MEMBER |
vuejs | core | 981,057,999 | 5,007 | LinusBorg | What problem does that solve? How is this better than simply assigning a custom property to `document.body.style`?
Is the scoping of the variable name solving any naming collision issues you would face with a non-scoped global name? Or wouldn't that rather be a hindrance as we are dealing with global custom properti... | 2021-11-28T10:12:51 | 2021-11-28T10:28:37 | {
"+1": 3
} | MEMBER |
vuejs | core | 982,362,133 | 5,018 | LinusBorg | Seems we expose the wrong proxy here. | 2021-11-30T07:37:07 | 2021-11-30T07:37:07 | {} | MEMBER |
vuejs | core | 975,165,979 | 4,982 | ygj6 | look: https://github.com/vuejs/vue-next/issues/4294#issuecomment-896082769 You can declare SampleProps in app.vue
eg:
```vue
<script lang='ts'>
export interface SampleProps{
sample1?:string;
sample2?:string;
}
</script>
<script setup lang="ts">
import { ref } from 'vue'
import SampleProps from ... | 2021-11-22T06:19:46 | 2021-11-22T06:32:38 | {} | MEMBER |
vuejs | core | 979,650,490 | 4,807 | yyx990803 | FYI I reverted this in 6d46b36e since it turns out to be breaking existing type expectations.
Could you please provide a reproduction of the original case where your types were failing so we can look for a better fix? | 2021-11-26T02:55:28 | 2021-11-26T04:32:26 | {} | MEMBER |
vuejs | core | 982,663,922 | 5,023 | posva | executed: https://v3.vuejs.org/api/instance-methods.html#watch | 2021-11-30T14:01:45 | 2021-11-30T14:01:45 | {} | MEMBER |
vuejs | core | 976,583,586 | 4,950 | kadiryazici | @yuwu9145 for example components that I created. https://github.com/teamseodo/simplebar-vue3/ | 2021-11-23T14:05:13 | 2021-11-23T14:05:22 | {} | CONTRIBUTOR |
vuejs | core | 977,198,820 | 4,950 | yuwu9145 | `"vue": "^3.2.16"` | 2021-11-23T21:50:55 | 2021-11-23T21:50:55 | {} | CONTRIBUTOR |
vuejs | core | 977,395,475 | 3,933 | fnlearner | when I use teleport whose to is shadow root, there is also a relatively long time until the click handler will be registered (about 5 seconds) | 2021-11-24T02:02:06 | 2021-11-24T02:02:06 | {} | NONE |
vuejs | core | 978,096,749 | 4,662 | adamdehaven | @raffobaffo would your solution also inject styles into the shadow DOM from child components imported within the `defineCustomElement` component that originate from external packages?
As an example, if I define and export a component with `defineCustomElement`, but within that element is a button component that is ... | 2021-11-24T17:46:20 | 2021-11-24T20:45:06 | {} | NONE |
vuejs | core | 980,638,780 | 4,662 | adamdehaven | @raffobaffo would you be willing to update your reproduction repo linked above with a new branch that utilizes your fix? I tried what you have but wasn't able to get it working for some reason. Would be much appreciated! | 2021-11-27T14:50:47 | 2021-11-27T14:51:02 | {} | NONE |
vuejs | core | 981,310,565 | 4,654 | Tommychou | Still not solved，With the latest cli, or this problem @yyx990803
<img width="1367" alt="WechatIMG163" src="https://user-images.githubusercontent.com/11855799/143816342-2df7e60b-b1e3-4f4e-8597-1fc446540623.png">
<img width="1367" alt="WechatIMG162" src="https://user-images.githubusercontent.com/11855799/143816599-4c... | 2021-11-29T05:46:52 | 2021-11-29T06:03:28 | {} | NONE |
vuejs | core | 981,342,717 | 4,964 | lmiller1990 | Since this is a VTU `shallowMount` specific feature, I have no real problem patching it there instead (bit hacky, but `shallowMount` in general is quite a hack).
Either way, let's make a decision so we can unblock the people wanting to update their Ionic version [see here for more](https://github.com/ionic-team/ioni... | 2021-11-29T07:04:20 | 2021-11-29T07:05:40 | {
"rocket": 1
} | MEMBER |
vuejs | core | 981,538,431 | 5,007 | olemarius | I agree that my problem can be solved in a different way, but it would be a nice-to-have feature to be able to do --my-var: v-bind(color) where --my-var is scoped to body, but considering v-bind generated css vars are scoped to component via inline style I suspect this is not possible with how things work today. I'll m... | 2021-11-29T11:16:31 | 2021-11-29T11:16:31 | {
"+1": 1
} | NONE |
vuejs | core | 779,308,808 | 3,235 | LinusBorg | I think two problems, combined, led to this effect:
`@click="log('Test')"` generates an inline function: `() => log('Test')`, which make the inner component update, technically, the passed listener changed. The SFC compiler can cache these kinds of inline function, but the runtime compiler that you are using, can't.... | 2021-02-15T15:51:52 | 2021-02-15T16:12:10 | {} | MEMBER |
vuejs | core | 781,248,537 | 2,863 | rstoenescu | Hello. First of all, thank you for your work on the issue.
Since [my report](https://github.com/vuejs/vue-next/issues/3244) has been closed as duplicate of this one, I suggest you also bump the importance of the bug (currently set as p3-minor) and remove the "has workaround" tag. | 2021-02-18T10:36:10 | 2021-02-18T10:36:10 | {} | NONE |
vuejs | core | 781,813,906 | 3,257 | HcySunYang | Is this really a bug? I do not think so. As long as you execute the slot functions in setup, you will get this warning, which has nothing to do with whether you use functional components to wrap it.
```js
import { createApp, h, defineComponent } from 'vue'
const Comp = defineComponent({
setup(props, { slots }... | 2021-02-19T04:43:13 | 2021-02-19T04:43:13 | {
"+1": 1
} | MEMBER |
vuejs | core | 781,920,852 | 3,257 | plehnen | @HcySunYang But then I should get the warning too when I execute the MyComponent directly in App.vue (instead of MyContainer), right? But then there is no warning. so something seems to be wrong there...
A little bit of context of the bigger picture what I try to accomblish: I want to tell the parent component if an... | 2021-02-19T08:32:13 | 2021-02-19T08:32:13 | {} | NONE |
vuejs | core | 781,958,975 | 3,230 | HcySunYang | Another way to deal with the problem is that we parse the string type style into an object, but I think this has two shortcomings:
1. This eats up performance
2. The original intention has been changed, using `cssText` is still the correct way. | 2021-02-19T09:39:40 | 2021-02-19T09:39:40 | {} | MEMBER |
vuejs | core | 782,292,830 | 3,267 | LinusBorg | Duplicate of #3228 | 2021-02-19T19:29:55 | 2021-02-19T19:29:55 | {} | MEMBER |
vuejs | core | 783,429,845 | 1,600 | hawkeye64 | Here is my use-case. The slotted data is fetched and turned into markdown, which is then given to `innerHtml` at rendering time.
Currently, this code (trying to escape the fences, but Github apparently does not support that):
```html
<my-markdown>
Indented code
Inline `code`
// Some comments
... | 2021-02-22T14:52:46 | 2021-02-22T14:52:46 | {
"+1": 1
} | NONE |
vuejs | core | 778,985,926 | 3,233 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.56 KB (0%) |
| runtime-dom.global.prod.js | 26.95 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-15T06:37:57 | 2021-02-15T06:37:57 | {} | NONE |
vuejs | core | 780,484,021 | 3,224 | pikax | This is a tricky one, `Component` should be the most generic valid component type.
TSX requires a type with a constructor to be able to render, which causes problems because `Component` does not require a constructor, because `{}` is a valid vue component.
There's no good solution for this, I think the `Compone... | 2021-02-17T11:11:41 | 2021-02-17T11:11:41 | {} | MEMBER |
vuejs | core | 782,073,520 | 3,257 | HcySunYang | Ok, I made a PR to make the warning consistent when calling the slot function outside the render function.
However, more and more users request similar capabilities. They hope to call the slot function in the `setup` function to determine whether the slot content exists or meets expectations. Maybe we don’t need to ... | 2021-02-19T13:27:40 | 2021-02-19T13:27:40 | {
"+1": 6
} | MEMBER |
vuejs | core | 782,618,060 | 3,258 | nandi95 | Marked it as ready for review, so I can get some feedback | 2021-02-20T12:13:00 | 2021-02-20T12:13:00 | {} | CONTRIBUTOR |
vuejs | core | 783,117,696 | 3,277 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.57 KB (0%) |
| runtime-dom.global.prod.js | 26.96 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-22T06:17:32 | 2021-02-22T06:17:32 | {} | NONE |
vuejs | core | 778,986,653 | 3,234 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 40.57 KB (+0.03% 🔺) |
| runtime-dom.global.prod.js | 26.96 KB (+0.05% 🔺) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-15T06:39:15 | 2021-02-15T06:43:50 | {} | NONE |
vuejs | core | 779,238,433 | 3,235 | axelthat | @LinusBorg If you goto `src/App.vue`, there's this html in setup function:
```
const html = `
<component-renderer :html="'<p>Navbar</p>'" @click="log('Test')"></component-renderer>
<p>BODY</p>
<button @click="$store.state.count++">Add</button>
<div v-for="a in $store.state.count">{{ a }}</div>
`
```
As y... | 2021-02-15T13:54:13 | 2021-02-15T13:55:52 | {} | NONE |
vuejs | core | 779,520,320 | 3,224 | HcySunYang | I got your point | 2021-02-16T01:08:34 | 2021-02-16T01:08:34 | {} | MEMBER |
vuejs | core | 780,505,831 | 3,224 | KaelWD | I think with that you can't do `const Foo: ComponentTSX = props => h(...` | 2021-02-17T11:54:18 | 2021-02-17T11:54:18 | {} | CONTRIBUTOR |
vuejs | core | 781,245,874 | 2,863 | HcySunYang | This [issue](https://github.com/vuejs/vue-next/issues/3244) provides more easier reproduction.
@edison1105 , thanks for your PR first, but your PR didn't fix the root cause. As I said [here](https://github.com/vuejs/vue-next/issues/3244#issuecomment-780424820)
>Add notes here.
May need an instance stack: https:/... | 2021-02-18T10:31:21 | 2021-02-18T10:31:21 | {} | MEMBER |
vuejs | core | 781,490,989 | 3,254 | posva | It wasn't possible in Vue 2 (https://github.com/vuejs/vue/issues/6787) but I think this would be really helpful
| 2021-02-18T17:01:39 | 2021-02-18T17:01:39 | {} | MEMBER |
vuejs | core | 783,112,449 | 3,275 | HcySunYang | It has the same reason as https://github.com/vuejs/vue-next/issues/3270 | 2021-02-22T06:07:17 | 2021-02-22T06:07:17 | {
"+1": 1
} | MEMBER |
vuejs | core | 783,115,075 | 3,276 | Edge00 | @HcySunYang Thank you for replying! So what is the best way to visit all `v-for` slots? | 2021-02-22T06:12:30 | 2021-02-22T06:14:06 | {} | NONE |
vuejs | core | 783,937,207 | 3,286 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.57 KB (0%) |
| runtime-dom.global.prod.js | 26.96 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-23T06:12:22 | 2021-02-23T06:14:56 | {} | NONE |
vuejs | core | 781,237,069 | 3,244 | HcySunYang | Closed because of duplicate | 2021-02-18T10:15:54 | 2021-02-18T10:15:54 | {} | MEMBER |
vuejs | core | 782,791,715 | 3,271 | HcySunYang | This is expected, when you refer to a scope variable in an event handler, it cannot be cached, which means that every update will create a new event function, which will cause the component to update. | 2021-02-21T03:54:14 | 2021-02-21T03:54:14 | {} | MEMBER |
vuejs | core | 779,101,402 | 3,224 | HcySunYang | I mean use defineComponent to create components
```ts
const Comp = defineComponent({ /* ... */ })
```
Comp always conforms to the use in TSX | 2021-02-15T09:50:25 | 2021-02-15T09:50:25 | {} | MEMBER |
vuejs | core | 780,335,414 | 3,246 | HcySunYang | When a component just renders an empty string:
```js
const Comp = { render: () => '' }
```
the ssr result is: **nothing**
the client rendering result is: **Text Node**
This causes hydration failure, it can be reproduced with the test case shown below:
```js
test('empty string', async () => {
co... | 2021-02-17T06:27:54 | 2021-02-17T06:28:15 | {} | MEMBER |
vuejs | core | 780,424,820 | 3,244 | HcySunYang | Add notes here.
May need an instance stack: https://github.com/vuejs/vue-next/blob/master/packages/server-renderer/src/render.ts#L146-L158.
It is problematic to execute the `ssrRenderComponent` function within the `ssrRender` function:
```js
ssrRender() {
// it's equivalent to calling `ssrRender` recursive... | 2021-02-17T09:29:59 | 2021-02-17T09:29:59 | {} | MEMBER |
vuejs | core | 780,801,805 | 3,248 | pikax | #2758 has the same functionality(from the tests I have here), it infers the arguments names, IMO it just needs a few more tests and it looks good | 2021-02-17T19:38:22 | 2021-02-17T19:38:22 | {} | MEMBER |
vuejs | core | 781,215,967 | 3,244 | edison1105 | duplicate of #2863 | 2021-02-18T09:40:41 | 2021-02-18T09:40:41 | {} | MEMBER |
vuejs | core | 781,488,748 | 3,253 | LinusBorg | Good example - good as in: where it gets a bit philosophical.
* Mixins and composition functions both are used to share code like methods, data, lifecycle hooks etc, usually - not a whole component.
* `extend`, technically, is also just a mixin but can be used like you do - write a base component and then extend f... | 2021-02-18T16:58:29 | 2021-02-18T16:58:29 | {
"+1": 3
} | MEMBER |
vuejs | core | 783,114,385 | 3,276 | HcySunYang | This is because `v-for` will generate a `Fragment` node. | 2021-02-22T06:11:08 | 2021-02-22T06:11:08 | {} | MEMBER |
vuejs | core | 778,987,097 | 2,764 | edison1105 | > You can try this in your local with your PR [codepen.io/hcysunyang/pen/YzpZyQW](https://codepen.io/hcysunyang/pen/YzpZyQW)
>
> I found a better way #3230
got the point. | 2021-02-15T06:40:08 | 2021-02-15T06:40:08 | {} | MEMBER |
vuejs | core | 779,175,538 | 3,235 | LinusBorg | Your reproduction doesnt do what it describes. It has a store but doesn't use them for any kind of loop.
Please provide a complete reproduction that actually demonstrates the problem. | 2021-02-15T11:59:47 | 2021-02-15T11:59:47 | {} | MEMBER |
vuejs | core | 779,247,734 | 3,236 | HcySunYang | Duplicate of https://github.com/vuejs/vue-next/issues/2370, you should use the `markRaw`:
```js
this.canvas = markRaw(new fabric.Canvas(can));
```
https://v3.vuejs.org/api/basic-reactivity.html#markraw | 2021-02-15T14:11:01 | 2021-02-15T14:11:01 | {
"+1": 3
} | MEMBER |
vuejs | core | 779,305,164 | 3,237 | LinusBorg | you change state while rendering (`test++`), triggering a re-render, and so on. Don't do that. | 2021-02-15T15:46:18 | 2021-02-15T15:46:29 | {} | MEMBER |
vuejs | core | 779,609,313 | 3,204 | dependabot-preview[bot] | Superseded by #3239. | 2021-02-16T06:13:38 | 2021-02-16T06:13:38 | {} | CONTRIBUTOR |
vuejs | core | 780,208,144 | 2,827 | daniesg | At the very least a console warning would be nice. This would be a very difficult bug to fix in a larger app. | 2021-02-17T00:32:11 | 2021-02-17T00:32:11 | {
"+1": 3
} | NONE |
vuejs | core | 781,857,643 | 3,260 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.57 KB (0%) |
| runtime-dom.global.prod.js | 26.96 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-19T06:22:59 | 2021-02-19T06:22:59 | {} | NONE |
vuejs | core | 781,857,881 | 3,261 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.57 KB (0%) |
| runtime-dom.global.prod.js | 26.96 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-19T06:23:27 | 2021-02-19T06:23:27 | {} | NONE |
vuejs | core | 782,997,598 | 3,274 | HcySunYang | I don't see any benefit from your proposal, templates are different from jsx, mixing them will only cause more confusion. And also, if you are requesting new features, you should go through an RFC, https://github.com/vuejs/rfcs | 2021-02-22T02:34:48 | 2021-02-22T02:34:48 | {} | MEMBER |
vuejs | core | 783,935,639 | 3,260 | dependabot-preview[bot] | Superseded by #3282. | 2021-02-23T06:08:42 | 2021-02-23T06:08:42 | {} | CONTRIBUTOR |
vuejs | core | 779,832,171 | 3,211 | tcstory | met the same problem | 2021-02-16T13:20:15 | 2021-02-16T13:20:15 | {} | NONE |
vuejs | core | 780,769,792 | 3,248 | posva | This seems more complete than https://github.com/vuejs/vue-next/pull/2589 and https://github.com/vuejs/vue-next/pull/2758 | 2021-02-17T18:47:24 | 2021-02-17T18:47:24 | {} | MEMBER |
vuejs | core | 782,590,852 | 3,270 | HcySunYang | This is because the `helloWorld` is analyzed as the binding of `setup`(SETUP_MAYBE_REF) when `compileScript` analyzes the bindings. It will generate the following code:
```ts
export function render(_ctx, _cache, $props, $setup, $data, $options) {
return (_openBlock(), _createBlock(_Fragment, null, [
_hoiste... | 2021-02-20T08:59:22 | 2021-02-20T08:59:22 | {} | MEMBER |
vuejs | core | 779,216,396 | 3,236 | Gavin-Dreyer | @asturur | 2021-02-15T13:14:42 | 2021-02-15T13:14:42 | {} | NONE |
vuejs | core | 781,492,461 | 3,254 | nandi95 | Amazing ❤️
I'll give this a go. | 2021-02-18T17:03:50 | 2021-02-18T17:03:50 | {} | CONTRIBUTOR |
vuejs | core | 783,115,120 | 3,275 | HcySunYang | Same workaround as https://github.com/vuejs/vue-next/issues/3270#issuecomment-782591109 | 2021-02-22T06:12:36 | 2021-02-22T06:12:36 | {} | MEMBER |
vuejs | core | 783,121,526 | 3,276 | HcySunYang | You need to manually crawl the `Fragment`'s children, see https://codesandbox.io/s/bold-sunset-c0hpg?file=/src/components/HelloWorld.vue | 2021-02-22T06:24:58 | 2021-02-22T06:24:58 | {
"+1": 2,
"laugh": 2
} | MEMBER |
vuejs | core | 779,832,578 | 2,386 | tcstory | met the same problem. I hope it be fixed soon | 2021-02-16T13:20:55 | 2021-02-16T13:20:55 | {
"+1": 1
} | NONE |
vuejs | core | 781,297,452 | 2,349 | shameleo | I rethinked my [issue](https://github.com/vuejs/vue-next/issues/2349#issuecomment-721576999) and created abstract component instead of directive. Maybe it will help somebody
<details>
<summary>Code is here</summary>
```javascript
// MIT License
import { withDirectives, onActivated } from 'vue';
... | 2021-02-18T12:06:34 | 2021-02-18T13:09:53 | {} | NONE |
vuejs | core | 781,562,579 | 3,256 | emirotin | For me it does
I focus the input
Press down the Ctrl key
Release it
The counter increases
Same reproducible with the Shift key
Now I feel satisfied paying back to the FOSS community
I don't like the tone of this conversation and am not interested continuing it in this mode | 2021-02-18T18:53:41 | 2021-02-18T18:53:41 | {} | NONE |
vuejs | core | 781,887,507 | 3,264 | HcySunYang | This will be fixed in https://github.com/vuejs/vue-next/pull/3230, as a workaround, you can use `v-if` instead of `v-show`. | 2021-02-19T07:23:44 | 2021-02-19T07:36:18 | {
"+1": 2
} | MEMBER |
vuejs | core | 782,332,305 | 3,268 | TheDutchCoder | To clarify, if you remove the `{{ hello }}` from the template it works correctly and `ssrInterpolate` is only imported once. | 2021-02-19T20:40:29 | 2021-02-19T20:40:29 | {} | NONE |
vuejs | core | 783,118,186 | 3,278 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.57 KB (0%) |
| runtime-dom.global.prod.js | 26.96 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-22T06:18:29 | 2021-02-22T06:18:29 | {} | NONE |
vuejs | core | 781,404,378 | 3,253 | LinusBorg | Your confusion likely stems from ambiguous terms:
* "Composition" as a general term refers to ways in which component logic can be extracted, re-used, and composed in multiple components.
* "The Composition API" refers to all the features provided by and used in `setup()`.
Composition can be achieved by using `... | 2021-02-18T15:01:16 | 2021-02-18T15:05:58 | {} | MEMBER |
vuejs | core | 782,548,618 | 1,352 | SilentDepth | Seems like this problem still exists in Vue 3.0.5 when using bundler.
Repro: https://codesandbox.io/s/vue-3-transition-comment-issue-chjvl | 2021-02-20T03:18:58 | 2021-02-20T03:18:58 | {} | NONE |
vuejs | core | 783,851,946 | 3,281 | HcySunYang | You should also make `@vue/server-renderer` external. Finally, I recommend you to use `webpack-node-externals`:
```js
const path = require('path');
const nodeExternals = require('webpack-node-externals')
module.exports = {
entry: './ssrapp2.js',
output: {
filename: 'bundled.js',
path: path.resolve(__d... | 2021-02-23T03:32:17 | 2021-02-23T03:32:17 | {} | MEMBER |
vuejs | core | 779,366,031 | 3,224 | KaelWD | We do, this is for a config that people can pass components into:
```js
new Vuetify({
iconSets: {
fa5: FontAwesomeIcon
}
})
```
I need a type that both:
- Accepts components of any type (functional or defineComponent)
- Lets me render that component (`<options.iconSets.fa5 />`)
> use defineCompon... | 2021-02-15T17:35:15 | 2021-02-15T17:35:23 | {} | CONTRIBUTOR |
vuejs | core | 779,570,439 | 3,238 | egoist | 👌 Just took a look at the code, it seems to be an intentional design | 2021-02-16T04:18:33 | 2021-02-16T04:18:33 | {} | NONE |
vuejs | core | 779,610,568 | 3,240 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.57 KB (0%) |
| runtime-dom.global.prod.js | 26.96 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-16T06:16:17 | 2021-02-16T06:16:17 | {} | NONE |
vuejs | core | 780,776,752 | 3,070 | araratmartirossyan | I still have this issue with vite. A patch that I found in the issue fixed it but only for dev. After build it's coming back. Any updates on how it can be fixed on build time? | 2021-02-17T18:58:30 | 2021-02-17T18:58:30 | {} | NONE |
vuejs | core | 781,257,959 | 2,863 | HcySunYang | @rstoenescu A workaround for your report:
```js
// Home.vue
const ComponentA = {
setup () {
return () => h('div')
}
}
const MyX = {
setup () {
return () => h('div')
}
}
export default {
setup () {
return {
myComponentName: ComponentA
}
}
}... | 2021-02-18T10:52:39 | 2021-02-18T10:52:39 | {} | MEMBER |
vuejs | core | 781,485,932 | 3,256 | posva | This is working as expected: it increments only if you keep ctrl pressed and press+release a different key. | 2021-02-18T16:54:26 | 2021-02-18T17:23:31 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.