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 | 764,189,416 | 3,073 | Kingbultsea | wait | 2021-01-21T02:26:11 | 2021-01-21T02:26:11 | {} | CONTRIBUTOR |
vuejs | core | 764,204,160 | 2,834 | Ryan2128 | Why is this PR still not merged? | 2021-01-21T03:12:42 | 2021-01-21T03:12:42 | {} | NONE |
vuejs | core | 766,585,123 | 1,696 | Timmitry | @ianef Yes, what you described was exactly my problem, too. Since this regression seems to be a won't-fix, we came up with another solution - namely parsing the (json-encoded) html-attributes before creating the vue app, and then passing them along as props. Something like:
```js
import { createApp } from 'vue';
i... | 2021-01-25T06:42:32 | 2021-01-25T06:42:32 | {} | NONE |
vuejs | core | 767,273,807 | 3,095 | eczn | #3096 implementation of this with TS feature of `LibraryManagedAttributes` & `Template Type`, it needs ts v4.1 | 2021-01-26T03:34:49 | 2021-01-26T03:38:29 | {} | NONE |
vuejs | core | 767,538,774 | 3,101 | 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).
---
You can also use the generated templates from vu... | 2021-01-26T13:25:00 | 2021-01-26T13:25:21 | {} | MEMBER |
vuejs | core | 768,080,631 | 3,090 | techbirds | Test:
without webpack bundle. run with only vue framework.
v2
v3
![image](https://... | 2021-01-27T07:03:35 | 2021-01-27T07:03:35 | {} | NONE |
vuejs | core | 768,117,980 | 3,108 | alreadytaken1990 | just in codepin miss that, see orgin code in runtime | 2021-01-27T08:21:33 | 2021-01-27T08:21:33 | {} | NONE |
vuejs | core | 768,388,962 | 2,855 | LinusBorg | Workaround:
```vue
<script lang="ts" setup>
import {
Teleport as teleport_,
TeleportProps,
VNodeProps
} from 'vue'
const Teleport = teleport_ as {
new (): {
$props: VNodeProps & TeleportProps
}
}
</script>
<template>
<component :is="Teleport">
</component>
</template>
``` | 2021-01-27T16:03:27 | 2021-01-27T16:03:27 | {
"+1": 9,
"-1": 4
} | MEMBER |
vuejs | core | 764,411,489 | 1,589 | rightaway | @HcySunYang @yyx990803 is this PR why https://vuejs.org/v2/style-guide/#v-if-v-else-if-v-else-without-key-use-with-caution was removed from style guide for Vue 3? It not necessary anymore to use `key` on `v-if` or `v-else`? | 2021-01-21T06:25:14 | 2021-01-21T06:25:14 | {} | NONE |
vuejs | core | 764,535,606 | 3,077 | 07akioni | Here are my expected types. Does anyone has different opinions?
|Format|Expected Prop Type|Current Behavior|
|-|-|-|
|`name: String`|`string \| undefined`|✅|
|`name: String as PropType<X>`|`X \| undefined`|✅|
|`name: { type: String, default: undefined }`|`string \| undefined`|`string`|
|`name: { type: String as P... | 2021-01-21T10:25:09 | 2021-01-21T10:25:09 | {
"+1": 5
} | CONTRIBUTOR |
vuejs | core | 767,489,356 | 3,100 | anarkh | I have the same situation | 2021-01-26T11:44:17 | 2021-01-26T11:44:17 | {} | NONE |
vuejs | core | 768,294,565 | 3,060 | HcySunYang | Closed because it's now available | 2021-01-27T13:44:42 | 2021-01-27T13:44:42 | {} | MEMBER |
vuejs | core | 763,519,033 | 3,066 | HcySunYang | This PR has a flaw, consider the following:
```js
const foo = ref([1])
watch(foo, () => {
console.log('should trigger')
})
foo.value = foo.value.slice()
```
with your PR, resulting in not triggering the `cb` correctly. Here we should check whether the source of observation is really an array.
| 2021-01-20T10:52:57 | 2021-01-20T10:52:57 | {
"eyes": 1
} | MEMBER |
vuejs | core | 766,275,806 | 2,791 | valq7711 | I found a terrible (but working) solution:
define a property directly on an instance
```javascript
// in beforeCreate-hook
const foo = computed(getter/setter)
Object.defineProperty(this, 'foo', {
enumerable: true,
configurable: true,
get: ()=> foo.value,
set: (v)=> foo.value=v
})
```
| 2021-01-24T02:09:15 | 2021-01-24T02:09:15 | {} | NONE |
vuejs | core | 766,690,060 | 3,094 | posva | Track at https://github.com/vuejs/vue-next/pull/2710
Please don't spam issues | 2021-01-25T09:45:13 | 2021-01-25T09:45:13 | {} | MEMBER |
vuejs | core | 767,377,662 | 3,090 | techbirds | 1、on the production build with `npm run build`
2、run as `http-server`
v2 perf:
v3 perf:... | 2021-01-26T08:14:08 | 2021-01-26T08:14:08 | {} | NONE |
vuejs | core | 767,874,569 | 1,539 | milochristiansen | I ran into this same issue. I needed to wrap elements from a slot and there was no way to do it in a normal template, so I had to make a render function. However, that broke all my scoped CSS.
Why in the hell is a "-s" being added to the scope IDs of render function output and how can it be made to stop doing it?
... | 2021-01-26T22:39:40 | 2021-01-26T22:46:57 | {
"+1": 3
} | NONE |
vuejs | core | 763,531,887 | 3,069 | posva | this seems to happen only with Vite but not with cli, please open an issue on Vite's repository https://github.com/vitejs/vite | 2021-01-20T11:14:22 | 2021-01-20T11:14:22 | {} | MEMBER |
vuejs | core | 764,210,778 | 3,075 | HcySunYang | If you are requesting new features, you should go through an RFC, https://github.com/vuejs/rfcs. | 2021-01-21T03:34:25 | 2021-01-21T03:34:25 | {} | MEMBER |
vuejs | core | 766,414,097 | 1,696 | ianef | Well I think there is something fundamentally wrong here.
In Vue 2 I used to be able to set data attributes on the app HTML element and retrieve them in the beforeMount method. If I used a render method this would replace the outer element thus removing the HTML that constituted the data being passed to Vue from the... | 2021-01-24T19:03:36 | 2021-01-24T19:09:04 | {} | NONE |
vuejs | core | 766,831,328 | 2,841 | devmount | Same here. I'm using Shoelace webcomponents with the current Vue 3.0.5 and can't catch events like `sl-show` from it.
I've created a [minimal working example](https://jsfiddle.net/devmount/17n52fxa/) and also described it at https://github.com/shoelace-style/shoelace/discussions/310. | 2021-01-25T13:53:12 | 2021-01-25T14:01:02 | {} | NONE |
vuejs | core | 767,074,066 | 2,753 | LongTengDao | @posva Hi~ I saw this PR was not released in 3.0.5. Is here any problem left? Will this be merged in 3.0.6? Thanks~ | 2021-01-25T19:55:31 | 2021-01-25T19:55:31 | {} | CONTRIBUTOR |
vuejs | core | 763,511,978 | 3,059 | posva | Closing in favor #3068 | 2021-01-20T10:40:36 | 2021-01-20T10:40:36 | {} | MEMBER |
vuejs | core | 764,153,695 | 2,851 | lijingfaatcumt | > @lijingfaatcumt Not having 2 distinct instances for the same object is good, but I still have concerns with the concept of having both a deep and a shallow versions of the same object graph and all the unexpected behaviours it leads to.
>
> It will unwillingly lead to having both raw and reactive versions of insta... | 2021-01-21T01:19:57 | 2021-01-21T01:24:50 | {} | NONE |
vuejs | core | 765,482,823 | 3,074 | posva | Nice! 🙌 | 2021-01-22T15:26:11 | 2021-01-22T15:26:11 | {} | MEMBER |
vuejs | core | 766,611,767 | 3,092 | HcySunYang | 你可以提供一个 wrapper 组件，我给你提供了一个例子：https://codesandbox.io/s/nervous-mcnulty-necyx?file=/src/App.vue | 2021-01-25T07:33:38 | 2021-01-25T07:33:38 | {
"+1": 1
} | MEMBER |
vuejs | core | 768,071,535 | 3,107 | HcySunYang | I not sure, but I think we should list the changes to the binding of custom directives in the migration guide. https://v3.vuejs.org/guide/migration/custom-directives.html | 2021-01-27T06:43:47 | 2021-01-27T06:43:47 | {
"+1": 1
} | MEMBER |
vuejs | core | 768,150,000 | 3,106 | HcySunYang | I created a [new project](https://github.com/HcySunYang/vue3-ssr-test) based on [the project](https://github.com/aprilcai/vue3-ssr-test) provided by @aprilcai, which provides four heap memory snapshots:
- [leak.start.heapsnapshot](https://github.com/HcySunYang/vue3-ssr-test/blob/master/leak.start.heapsnapshot)
- [l... | 2021-01-27T09:19:50 | 2021-01-27T09:22:24 | {
"+1": 1
} | MEMBER |
vuejs | core | 764,562,946 | 3,074 | posva | Will this fix it only on dev though? 🤔 | 2021-01-21T11:14:06 | 2021-01-21T11:14:06 | {} | MEMBER |
vuejs | core | 764,610,702 | 3,082 | edison1105 | relate #3078 | 2021-01-21T12:29:30 | 2021-01-21T12:29:30 | {} | MEMBER |
vuejs | core | 765,851,739 | 3,087 | HcySunYang | Check out https://v3.vuejs.org/api/application-config.html#optionmergestrategies | 2021-01-23T03:23:59 | 2021-01-23T03:23:59 | {} | MEMBER |
vuejs | core | 766,120,056 | 3,088 | zce | https://github.com/vuejs/vue-next/blob/fd16f2bd7844107eab3155d58162a63da9a701bf/packages/compiler-sfc/src/compileScript.ts#L601-L607 | 2021-01-23T16:24:03 | 2021-01-23T16:24:03 | {} | NONE |
vuejs | core | 767,600,783 | 3,099 | LinusBorg | I'd personally rather make the change I proposed. The value may not be cached, but you will likely access it once only in that hook, so there's no real performance impact to be expected. | 2021-01-26T14:59:30 | 2021-01-26T14:59:30 | {
"+1": 1
} | MEMBER |
vuejs | core | 768,199,572 | 3,107 | posva | @xiachaoxulu can you open a PR or an issue at https://github.com/vuejs/docs-next to add the removal of binding.expression to the list of breaking changes | 2021-01-27T10:46:13 | 2021-01-27T10:46:13 | {} | MEMBER |
vuejs | core | 763,415,608 | 3,059 | posva | I don't understand what problem are you trying to highlight. There is no watch in your code. Can you take a look at other issues to provide proper reproduction steps? | 2021-01-20T08:04:42 | 2021-01-20T08:04:42 | {} | MEMBER |
vuejs | core | 763,437,909 | 3,067 | Kingbultsea | ```javascript
let a = {}
let b = a
expect(a === b).toBe(true)
``` | 2021-01-20T08:46:21 | 2021-01-20T08:46:21 | {} | CONTRIBUTOR |
vuejs | core | 763,449,954 | 3,065 | posva | This is worth going through an RFC, can you open a discussion there or a proposal? | 2021-01-20T09:02:14 | 2021-01-20T09:02:14 | {} | MEMBER |
vuejs | core | 765,481,019 | 3,084 | posva | IMO keeping them as comments to remind that these properties are important for the desired behavior would be helpful | 2021-01-22T15:23:17 | 2021-01-22T15:23:17 | {} | MEMBER |
vuejs | core | 767,495,239 | 3,090 | posva | I used the code generated by `yarn create @vitejs/app` and migrated it to options api with Vue CLI and Vue 2 to compare. As @LinusBorg pointed out in discussions, it could be related to differences between the bundling (webpack vs rollup). Maybe there is something to improve here but not sure where | 2021-01-26T11:56:17 | 2021-01-26T11:56:17 | {} | MEMBER |
vuejs | core | 990,783,550 | 2,279 | kepi0809 | fixed this problem this way:
```js
<component
v-bind="(({ is, ...o }) => o)(componentOptions)"
:is="componentOptions.is"
</component>
```
yes, it looks hacky but it works and this way `is` won't show up in the rendered HTML as an attribute on the rendered component. | 2021-12-10T09:41:05 | 2021-12-10T09:41:05 | {
"+1": 1
} | NONE |
vuejs | core | 992,736,807 | 3,044 | pleek91 | My use case is a clone function where I want to accept any reactive object and return the a new object of the exact same type.
```javascript
const source = reactive({ hello: 'world' })
const copy = clone(source)
source.hello = 'bob'
copy.hello // 'world'
```
But there's an issue if you pass in something... | 2021-12-13T18:08:59 | 2021-12-13T18:08:59 | {} | NONE |
vuejs | core | 993,116,666 | 5,102 | lidlanca | https://v3.vuejs.org/guide/migration/suspense.html#child-updates
```js
<suspense>
<asyncC1 v-if='toggle'>
<asyncC2 v-else>
<template #fallback>
Loading...
</template>
</suspense>
```
[sfc playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbiAgaW1wb3J0IHtcbiAgICBoLF... | 2021-12-14T03:14:41 | 2021-12-14T03:23:56 | {} | CONTRIBUTOR |
vuejs | core | 993,160,221 | 5,102 | robertmoura | Yeah, you hit the nail on the head there. Wrapping async components in a div stops it from returning into the pending state ([sfc.vuejs.org/]).
Are there any intensions to rework the spec to handle some of these cases? Vue warns me that it's experimental and subject to changes but I haven't heard of any movement on ... | 2021-12-14T05:02:09 | 2021-12-14T05:02:09 | {} | NONE |
vuejs | core | 993,169,375 | 1,033 | abhic91 | Thanks olemarius.
Adding this fixed it
```
// tsconfig.json
{
"compilerOptions": {
// ...
"types": [
"vite/client", // if using vite
// ...
]
}
}
``` | 2021-12-14T05:22:24 | 2021-12-14T05:22:24 | {
"+1": 1
} | NONE |
vuejs | core | 995,857,028 | 5,105 | caozhong1996 | Note: it's very similar to #4339
I love this pr, only a small change which is enough for the demand. But I have a question, it seems that we can control cache via key now, why do we need expose `pruneCacheEntry`? Can you add some test? | 2021-12-16T14:16:25 | 2021-12-16T14:53:42 | {} | CONTRIBUTOR |
vuejs | core | 993,891,053 | 5,106 | lidlanca | for a static vnode chunk created by the compiler `createStaticVNode` styles are being merged staticall if the input is an array of objects.
for the none static case(patchStyle) does not have handling logic for array of objects | 2021-12-14T19:06:56 | 2021-12-14T19:06:56 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 990,676,505 | 5,071 | yyx990803 | This is not supported. Directives must be constantly applied. | 2021-12-10T07:18:25 | 2021-12-10T07:18:25 | {} | MEMBER |
vuejs | core | 990,679,378 | 5,085 | yyx990803 | Don't use the React JSX transform for Vue... they are not the same.
For Vue 3 you should be using https://github.com/vuejs/jsx-next | 2021-12-10T07:23:45 | 2021-12-10T07:23:45 | {} | MEMBER |
vuejs | core | 993,216,405 | 5,104 | zhangenming | So why can't we improve him? Is there any other reason? thanks | 2021-12-14T06:58:16 | 2021-12-14T06:58:16 | {} | CONTRIBUTOR |
vuejs | core | 993,498,005 | 5,104 | caozhong1996 | Only stand for my personal view:
````vue
<script setup>
import { computed, onUpdated, ref, toRefs } from 'vue'
const props = defineProps({
value: Number,
})
const { value } = toRefs(props)
// If we can do this
// const { value } = toRefs(defineProps({
// value: Number,
// }))
// How about this?... | 2021-12-14T12:37:02 | 2021-12-14T12:37:02 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 998,138,641 | 4,707 | robmadole | Using the standard SVG + JavaScript version of Font Awesome is not recommended. Check out the official Vue component we have https://github.com/FortAwesome/vue-fontawesome | 2021-12-20T17:40:59 | 2021-12-20T17:40:59 | {} | NONE |
vuejs | core | 998,264,103 | 5,142 | posva | This was intentionally left out and discussed in the relevant RFCs | 2021-12-20T20:58:34 | 2021-12-20T20:58:34 | {} | MEMBER |
vuejs | core | 989,643,258 | 5,081 | posva | As a workaround `delete` the `innerHTML` property if you want to pass children | 2021-12-09T08:57:27 | 2021-12-09T08:57:27 | {
"eyes": 1
} | MEMBER |
vuejs | core | 990,027,423 | 5,041 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/4736#issuecomment-934212424 | 2021-12-09T16:45:59 | 2021-12-09T16:46:05 | {} | MEMBER |
vuejs | core | 992,456,825 | 1,033 | olemarius | Hi,
Try this in your tsconfig.json file
```json
"exclude": [
"**/node_modules",
"**/dist",
// https://github.com/johnsoncodehk/volar/discussions/592
"**/*.stories.ts"
]
``` | 2021-12-13T13:05:05 | 2021-12-13T13:05:22 | {
"+1": 2
} | NONE |
vuejs | core | 996,537,929 | 5,132 | imbyungjun | I want to see the original SFC style source code in the Chrome devtool to debug with it. Just like when it working without typescript.
I'm really confusing this issue will be fixed or not.
In https://github.com/vuejs/vue-cli/issues/2978, there no more progress to solve this kind of issue but,
[one of the blog pos... | 2021-12-17T08:44:12 | 2021-12-17T08:44:12 | {} | NONE |
vuejs | core | 991,048,319 | 5,091 | LinusBorg | Workaround: Move the condition into the slot:
```html
<template #content>
<template v-if="stateBool">
<svg>.....
<div> ....
</template>
<template v-else>
<svg>.....
<div> ....
</template>
</template>
``` | 2021-12-10T15:06:51 | 2021-12-10T15:06:51 | {
"+1": 1
} | MEMBER |
vuejs | core | 991,258,332 | 5,092 | posva | Please search existing issues before opening new ones and 🙏 | 2021-12-10T20:03:42 | 2021-12-10T20:03:42 | {} | MEMBER |
vuejs | core | 991,984,805 | 5,096 | Rkaede | As a workaround for any components that provide a value I relay any parent values through a context object.
```javascript
// provide-b composition api example
setup(props) {
const context = inject('context', {});
provide('context', { ...context, b: props.b });
}
``` | 2021-12-12T22:42:56 | 2021-12-12T22:59:37 | {} | NONE |
vuejs | core | 993,100,264 | 5,085 | dolymood | @yyx990803
### The repo
I created a repo for support JSX runtime [vue-jsx-runtime](https://github.com/dolymood/vue-jsx-runtime) and examples [vue-jsx-runtime-examples](https://github.com/dolymood/vue-jsx-runtime-examples).
Runtime size:
- minify Iife: `2.53Kb` (no gzip)
- ES Module: 8.79kb (no minify)
... | 2021-12-14T02:37:18 | 2021-12-14T02:44:05 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 994,925,085 | 4,997 | awkj | Can Official support the Syntactic sugar？
https://github.com/anncwb/vite-plugin-vue-setup-extend
```
<template>
<div>hello world {{ a }}</div>
</template>
<script lang="ts" setup name="App">
const a = 1
</script>
``` | 2021-12-15T15:56:07 | 2021-12-15T15:56:07 | {
"+1": 9
} | NONE |
vuejs | core | 995,260,869 | 4,985 | BryceBarbara | Is this fix able to be ported to the composition-api package as well? | 2021-12-15T22:23:19 | 2021-12-15T22:23:19 | {} | NONE |
vuejs | core | 996,026,922 | 5,129 | posva | Or even passing `Partial<ISampleProps>` for optional props. | 2021-12-16T17:27:41 | 2021-12-16T17:27:41 | {} | MEMBER |
vuejs | core | 996,686,610 | 5,133 | posva | Hello, make sure to always provide a reproduction that follows the instructions at https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro.
Open a new issue with a reproduction that follows those instructions if you manage to create a boiled down reproduction. | 2021-12-17T12:30:02 | 2021-12-17T12:30:02 | {} | MEMBER |
vuejs | core | 997,174,559 | 3,869 | zhangyuang | >
What's your mean is i should use some library like `js-dom` and inserts `ctx.teleports` into the exactly dom node in server side? But if i use renderToNodeStream what should i do? | 2021-12-18T09:16:04 | 2021-12-18T09:16:04 | {} | CONTRIBUTOR |
vuejs | core | 990,678,131 | 5,084 | LinusBorg | I think you are confused about the process of unwrapping. What Unwrapping is, is [explained here](https://v3.vuejs.org/api/basic-reactivity.html#reactive): (green info box)
The return value of `setup` is not deeply unwrapped, however - only the top level properties are unwrapped.
so a ref nested in a non-reactiv... | 2021-12-10T07:21:19 | 2021-12-10T07:21:19 | {} | MEMBER |
vuejs | core | 990,962,018 | 5,090 | posva | This seems more confusing than the existing syntax, especially given than both are supported since `slot` would be used in different cases and could lead to breaking existing cases. If you still think this is worth pursuing, please follow the RFC process in the rfcs repo. | 2021-12-10T13:11:37 | 2021-12-10T13:11:37 | {} | MEMBER |
vuejs | core | 991,077,962 | 5,091 | sofienjoulak | thank you for your quick reply,
if anyone else have the same problem and interested in a different workaround this worked me :
Simply put the inline svg in a separate component and import it
```
<template>
< svg >
...
</ svg >
</template>
<script>
export default {
name: "AddSvg"
};... | 2021-12-10T15:43:17 | 2021-12-10T15:44:41 | {
"+1": 2
} | NONE |
vuejs | core | 991,229,654 | 4,397 | eggplantiny | ```ts
// HelloWorld.vue
const helloWorld = () => {
window.alert('Hello World')
}
defineExpose({ helloWorld })
```
```ts
// App.vue
const hello = ref<ComponentPublicInstance<typeof HelloWorld & { helloWorld: () => void }>>()
onMounted(() => {
hello.value?.helloWorld()
})
```
It can track IDE auto... | 2021-12-10T19:15:58 | 2021-12-10T19:37:47 | {
"+1": 1
} | NONE |
vuejs | core | 991,820,258 | 5,089 | yyx990803 | This would technically be a (type) breaking change though, it would break existing apps using `const key: InjectionKey<string> = Symbol();`?
This probably needs to be put in a minor release (where we by convention may ship type breaking changes) | 2021-12-12T01:57:28 | 2021-12-12T01:58:05 | {} | MEMBER |
vuejs | core | 992,025,804 | 5,086 | yyx990803 | If you do not intend to mutate the items in the list (e.g. they are server-fetched data), another way to improve performance with large lists is going immutable - mark the list with `markRaw` to prevent Vue from making it reactive, and trigger list updates by re-assigning the list: [example](https://sfc.vuejs.org/#eyJB... | 2021-12-13T01:20:19 | 2021-12-13T01:20:19 | {
"+1": 1
} | MEMBER |
vuejs | core | 995,601,728 | 5,121 | gitivon | > Do you have an actual reproduction? Because this seems to work:
>
> ```ts
> defineComponent({
> props: {
> value: String
> },
> setup(props) {
> const a = toRef(props, 'value')
> a.value
> }
> })
> ```
You can try this
```tsx
import { defineComponent, PropType, toRef } from "vu... | 2021-12-16T09:39:45 | 2021-12-16T09:39:45 | {} | NONE |
vuejs | core | 995,887,198 | 5,127 | posva | I would say this is more correct since the component is rendered by a parent element that is not _kept alive_. It's like the need of using it with the `v-slot` syntax [in vue-router](https://next.router.vuejs.org/api/#router-view-s-v-slot) | 2021-12-16T14:49:27 | 2021-12-16T14:49:27 | {
"+1": 1
} | MEMBER |
vuejs | core | 997,347,713 | 4,707 | caozhong1996 | I would say it seems caused by Font Awesome.
https://github.com/Xulio-Xulio/VueJs-Pokedex/blob/b06d7e6814fd137a10b29181690af8618492abe1/pokedex/src/components/PokemonDetail.vue#L46
````html
<i v-else class="fas fa-spinner fa-spin"></i>
````
Remove those classes, everything will be all right.
````html
<i v-... | 2021-12-19T08:10:36 | 2021-12-19T08:10:36 | {} | CONTRIBUTOR |
vuejs | core | 998,162,392 | 4,735 | baermathias | Sounds great! @LinusBorg is it already possible to estimate when the docs will be done, so that Vue 3 will be the default version? | 2021-12-20T18:16:51 | 2021-12-20T18:16:51 | {} | NONE |
vuejs | core | 998,578,365 | 2,457 | ghost | 官方尽快解决这个问题啊，搁置了两个月了 | 2021-12-21T08:39:08 | 2021-12-21T08:39:08 | {} | NONE |
vuejs | core | 990,575,711 | 5,085 | caozhong1996 | I don't quite get your meaning, we already have jsx-next, what is the different? | 2021-12-10T03:22:31 | 2021-12-10T03:22:31 | {} | CONTRIBUTOR |
vuejs | core | 992,002,051 | 5,076 | lidlanca | https://html.spec.whatwg.org/multipage/syntax.html#attributes-2
I wonder in what standard duplicate attributes are allowed.
| 2021-12-13T00:18:38 | 2021-12-13T00:18:38 | {} | CONTRIBUTOR |
vuejs | core | 994,216,022 | 5,104 | zhangenming | ```
// If we can do this
// const { value } = toRefs(defineProps({
// value: Number,
// }))
```
But this is a common way to use it, we want props be reactive
or introduce a sugar grammar , make props be reactive by default | 2021-12-15T01:56:33 | 2021-12-15T01:56:33 | {} | CONTRIBUTOR |
vuejs | core | 992,622,349 | 5,080 | evnp | Thanks for the response, very interesting context. I (naively) did not read `for..in` as a performance choice above other options – indeed when running the above benchmarks on objects of size 10 as you suggest I see that `for..in` is quite a bit more performant than alternatives!*
Point taken – any issue that could... | 2021-12-13T16:00:25 | 2021-12-13T16:00:25 | {} | NONE |
vuejs | core | 993,886,977 | 5,107 | lidlanca | objects in array are merged in order.
your problem is that you are using "ambiguous" style properties and hence getting a less intuitive style expressed
`font-size` vs `font`
iterating in reverse will add additional complexity to the merge logic and probably more cost to runtime, since more checks need to be ... | 2021-12-14T19:01:52 | 2021-12-14T19:01:52 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 995,130,957 | 5,109 | lidlanca | recommending the usage of
```css
v-bind( '(a+b) + "px"' )
```
over
```css
v-bind( (a + b) + 'px' )
```
misses the point of this issue.
it will be interesting to get some more feedback why there is no place to address what is pointed in this issue.
considering that JS expression are actually suppor... | 2021-12-15T19:30:35 | 2021-12-16T05:52:25 | {} | CONTRIBUTOR |
vuejs | core | 995,942,933 | 5,129 | caozhong1996 | Try this:
````ts
interface ISampleProps {
foo: {
bar: string
}
}
const props = withDefaults(defineProps<ISampleProps>(), {
foo: () => {
return {
bar: '123'
}
}
})
```` | 2021-12-16T15:50:02 | 2021-12-16T15:50:02 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 990,742,385 | 5,087 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/2279 | 2021-12-10T08:46:13 | 2021-12-10T08:46:13 | {} | MEMBER |
vuejs | core | 991,657,202 | 4,993 | LinusBorg | I'll keep this open as a reference for the PR | 2021-12-11T14:11:08 | 2021-12-11T14:11:08 | {} | MEMBER |
vuejs | core | 994,225,262 | 5,104 | caozhong1996 | Yep, I'm with you, meanwhile, we'd better not open Pandora's Box. | 2021-12-15T02:14:33 | 2021-12-15T02:14:33 | {} | CONTRIBUTOR |
vuejs | core | 998,398,385 | 4,707 | fenghw2087 | > The issues that I am seeing that are throwing the same errors here are with using "vue-fontawesome" . I'll need to fully gut it out of my project but it seems that the project doesn't work well with vue-next. Issues occur when doing conditional rendering and show/hiding something on the page
I met some error in pr... | 2021-12-21T01:37:17 | 2021-12-21T01:37:17 | {
"+1": 1
} | NONE |
vuejs | core | 990,867,636 | 2,279 | kepi0809 | that will still render on the html `is="undefined"`
but yeah didn't check its performance, if it's true what you say then I suppose the best option is to create another computed property without the `is` attribute | 2021-12-10T10:54:42 | 2021-12-10T11:03:55 | {} | NONE |
vuejs | core | 991,643,218 | 4,552 | vaaski | I am running into a similar issue with custom css properties, I believe this is related.
| 2021-12-11T13:25:14 | 2021-12-11T13:25:14 | {
"eyes": 1
} | NONE |
vuejs | core | 991,862,952 | 5,089 | pikax | > This would technically be a (type) breaking change though, it would break existing apps using `const key: InjectionKey<string> = Symbol();`?
Yes | 2021-12-12T09:29:49 | 2021-12-12T09:29:49 | {} | MEMBER |
vuejs | core | 992,449,887 | 1,033 | abhic91 | I have the same problem. I get
```
Type '{ class: string; }' is not assignable to type 'DetailedHTMLProps<HTMLAttributes<HTMLDivElement>, HTMLDivElement>'.
Property 'class' does not exist on type 'DetailedHTMLProps<HTMLAttributes<HTMLDivElement>, HTMLDivElement>'. Did you mean 'className'?
```
@olemarius did y... | 2021-12-13T12:56:06 | 2021-12-13T12:56:58 | {} | NONE |
vuejs | core | 996,557,818 | 5,132 | imbyungjun | Okay,
It is just expected behavior at least in `vue-next` project.
`vue-cli` may handle kind of source map things. But, not sure cause it is a different project, right?
Thank you for answer! | 2021-12-17T09:15:49 | 2021-12-17T09:15:49 | {} | NONE |
vuejs | core | 996,656,751 | 5,133 | caozhong1996 | You can create a reproduction via https://sfc.vuejs.org/
看看能不能用这个复现： https://sfc.vuejs.org/ | 2021-12-17T11:39:09 | 2021-12-17T11:39:09 | {} | CONTRIBUTOR |
vuejs | core | 997,159,807 | 5,126 | zhangyuang | thanks，let me take a look
发自我的iPhone
------------------ Original ------------------
From: ygj6 ***@***.***>
Date: Sat,Dec 18,2021 3:17 PM
To: vuejs/vue-next ***@***.***>
Cc: yuuang ***@***.***>, Author ***@***.***>
Subject: Re: [vuejs/vue-next] bug(ssr): teleport render bug in ssr (Issue #5... | 2021-12-18T07:19:12 | 2021-12-18T07:19:12 | {} | CONTRIBUTOR |
vuejs | core | 998,148,175 | 4,707 | runxc1 | The issues that I am seeing that are throwing the same errors here are with using "vue-fontawesome" . I'll need to fully gut it out of my project but it seems that the project doesn't work well with vue-next. Issues occur when doing conditional rendering and show/hiding something on the page | 2021-12-20T17:56:36 | 2021-12-20T17:56:36 | {} | NONE |
vuejs | core | 990,173,700 | 5,080 | evnp | Looks like a similar issue exists in `normalizeStyle`. [Here's](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSc7XG5cbmNvbnN0IG1zZyA9IHJlZignSGVsbG8gV29ybGQhJyk7XG4gIFxuY29uc3Qgb3ZlcnJpZGVDb2xvclN0eWxlID0gW1wicmVkXCJdO1xub3ZlcnJpZGVDb2xvclN0eWxlLnRvU3RyaW5nID0gKCkgPT4gXCJjb... | 2021-12-09T19:40:32 | 2021-12-09T19:40:32 | {} | NONE |
vuejs | core | 701,266,701 | 2,279 | LinusBorg | Replacement can only work reliably if the presence of the `is` attribute is guaranteed. That is not the case when you are using the define object syntax, as that by nature means that there is in dynamic JavaScript expression involved, which during runtime, may or may not return an object with an `is` property.
While... | 2020-09-30T09:11:43 | 2021-12-10T10:07:51 | {
"+1": 3
} | MEMBER |
vuejs | core | 990,887,568 | 2,279 | kepi0809 | > @kepi0809 you sure? Afaik, undefined props are skipped
weird... this was the first approach I tried to fix this problem and it didn't seem to work then, but now I tested it again and it works with both `is: null` and `is: undefined`.
Thank you for for pointing again in that direction :+1: | 2021-12-10T11:22:52 | 2021-12-10T11:22:52 | {
"+1": 1
} | NONE |
vuejs | core | 991,153,335 | 4,695 | raffobaffo | Any update on this MR or on the feature in general? | 2021-12-10T17:21:27 | 2021-12-10T17:21:27 | {
"eyes": 3
} | NONE |
vuejs | core | 991,821,252 | 5,080 | yyx990803 | FWIW we use `for ... in` intentionally in many places, including on props objects. This is an intentional trade-off because using objects with custom prototypes as props/style/class binding objects is simply non-existent in practice. The case we are defending against is only possible in theory, but there isn't any reas... | 2021-12-12T02:07:14 | 2021-12-12T02:07:14 | {
"+1": 1
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.