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 | 737,634,989 | 2,694 | yyx990803 | `model` should be the source of truth, not the template. If the user intends to provide an initial value that is neither true-value or false-value, the value should be left untouched.
This actually has nothing to do with `true/false-value`. e.g. if you have `<input type="checkbox" v-model="model">` but `model`'s ini... | 2020-12-03T03:06:54 | 2020-12-03T03:06:54 | {} | MEMBER |
vuejs | core | 737,734,359 | 2,711 | hoiheart | I understand your kind answer, but I still have some questions.
- Based on the result code of renderToString using id or ref, Does not the server-side rendering code expose the teleport template?
- If made source using ref and v-if (<a href="https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/__test... | 2020-12-03T08:01:52 | 2020-12-03T08:01:52 | {} | NONE |
vuejs | core | 735,723,395 | 2,689 | posva | The things you propose have been discussed already and that's why there is an officially supported library vue-class-component. As a maintainer, I would appreciate if you search existing RFCs https://github.com/vuejs/rfcs before opening this kind of proposals, it would really save us time 🙂 | 2020-11-30T11:17:03 | 2020-11-30T11:17:03 | {} | MEMBER |
vuejs | core | 735,761,388 | 2,691 | edison1105 | ```javascript
app.config.globalProperties.$foo = 'hello'
```
usage
```javascript
created(){
console.log(this.$foo)
}
```
If you want to use it outside the component, maybe you can bind the data to the window or use Vuex to solve it. | 2020-11-30T12:38:10 | 2020-11-30T12:54:11 | {
"+1": 1
} | MEMBER |
vuejs | core | 735,885,023 | 2,692 | Jack-rainbow | Check out [731](https://github.com/vuejs/vue-next/issues/731) There are instructions to keep in alpha.5, but my test in version 3.0.3 did not take effect。
| 2020-11-30T16:14:33 | 2020-11-30T16:14:33 | {} | NONE |
vuejs | core | 735,922,400 | 2,692 | posva | 
Seems to work. Maybe you have some extension blocking the link from alicdn | 2020-11-30T17:16:46 | 2020-11-30T17:16:46 | {} | MEMBER |
vuejs | core | 736,020,765 | 2,568 | yyx990803 | The actual cause:
- `v-on` has its own special expression processing (it's skipped in `transformExpression`)
- However, it is not replacing the original `exp` on the directive node, so the scope ref check is checking the non-processed expression node.
The fix is ensure `v-on` replaces the original `exp` with the... | 2020-11-30T20:22:03 | 2020-11-30T20:22:03 | {} | MEMBER |
vuejs | core | 736,280,095 | 2,694 | edison1105 | I opened a PR,but I found that `true-value` and `false-value` are also not supported when `v-model` value is a `Set` or an `Array`.Is it designed like this? | 2020-12-01T07:28:50 | 2020-12-01T07:41:09 | {} | MEMBER |
vuejs | core | 736,612,836 | 2,220 | dev-itsheng | I agree with you, but I'm too busy to perfect the docs. If there is still no one doing this after one or two month , I will try it. | 2020-12-01T15:08:15 | 2020-12-01T15:08:15 | {} | CONTRIBUTOR |
vuejs | core | 737,101,887 | 2,709 | ChanningHan | > > 可惜
>
> 怎么了
碰巧之前也发现了这个问题 | 2020-12-02T09:20:10 | 2020-12-02T09:20:10 | {} | NONE |
vuejs | core | 737,651,696 | 2,195 | antfu | @basvanmeurs Sorry I missed your comment. The ability to "re-activate" a scope is indeed interesting. But as the `effect` is not `re-activatable` with the current implementation, I'd suggest you open a RFC to add the ability to resume a stopped `effect`. After that, we can easily adapt it to the `effectScope`. What do ... | 2020-12-03T04:05:13 | 2020-12-03T04:05:13 | {} | MEMBER |
vuejs | core | 737,156,590 | 2,706 | anotherso1a | Of course, it is debugging and analysis through breakpoints. The debugging part is the source code of Vue.
But I have decided to close this pr, the reason for this problem is that I am not so familiar with Vue | 2020-12-02T10:59:38 | 2020-12-02T10:59:38 | {} | NONE |
vuejs | core | 735,709,673 | 2,689 | John0King | @posva I do not care about `composition API`, and @edison1105 I know that repo ( and it's different than my proposal, it map class to use js object like api and it will missing many decorators in `vue-property-decorator` for vue3, and my proposal is about direct support class component instead of mapping , and... | 2020-11-30T10:50:03 | 2020-11-30T10:50:03 | {} | NONE |
vuejs | core | 735,891,488 | 2,692 | Jack-rainbow | I also tried svg2, but it didn’t work. | 2020-11-30T16:25:02 | 2020-11-30T16:25:02 | {} | NONE |
vuejs | core | 735,902,668 | 2,692 | Jack-rainbow | I use vue2.0 syntax svg appeared. Sorry, added a useless issuse。 | 2020-11-30T16:43:44 | 2020-11-30T16:43:44 | {} | NONE |
vuejs | core | 736,258,409 | 2,698 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.38 KB (0%) |
| runtime-dom.global.prod.js | 26.7 KB (0%) |
| size-check.global.prod.js | 16.18 KB (0%) | | 2020-12-01T06:41:59 | 2020-12-01T06:41:59 | {} | NONE |
vuejs | core | 736,646,986 | 2,701 | posva | Can you open an issue or pull request in the vuejs/docs-next repository? | 2020-12-01T16:01:34 | 2020-12-01T16:01:34 | {} | MEMBER |
vuejs | core | 736,924,866 | 2,694 | edison1105 | I think https://github.com/vuejs/vue-next/commit/48f00c0f1b574a235be40c560d2cf373be97615e is not fix this bug.
We should assign `true-value` or `false-value` to `checkbox` but `setChecked` is not do this after first render.
``` javascript
<div id="app">
<label>model {{ model }}</label>
<input type="checkbox"... | 2020-12-02T01:21:28 | 2020-12-02T01:21:28 | {} | MEMBER |
vuejs | core | 737,088,117 | 2,706 | anotherso1a | It was caused by my use of an external code. After an error was reported, it would be misleading when locating the wrong line number. There was no way to confirm the source of the problem in the first time.
.
What would fix is is changing `RouterView`'s render function so that it returns a single root when possible: https://jsfiddle.net/yyx990803/myv5e6zd/
| 2020-12-02T16:51:33 | 2020-12-02T16:51:33 | {
"+1": 1
} | MEMBER |
vuejs | core | 737,632,151 | 2,711 | meteorlxy | ~~IMO:~~
~~- With ref target, teleports can find the target in current component scope, so it's rendered to string directly.~~
~~- With id target, teleports cannot determine where the target is during SSR, so it's extracted to the context.~~ | 2020-12-03T02:59:33 | 2020-12-03T06:48:39 | {} | MEMBER |
vuejs | core | 736,272,799 | 2,689 | John0King | ~~@edison1105~~ @posva I read that a few month ago, that's why I open a new issue instead of talking in that closed issue again.
and it seems that you and your team is hate `class` for some reason, but IMO I like `class` because it provide best language feature and most consistent API surface (there no other way t... | 2020-12-01T07:14:11 | 2020-12-01T07:37:06 | {} | NONE |
vuejs | core | 736,300,031 | 2,699 | CHOYSEN | The original issue: https://github.com/vitejs/vite/issues/1160 | 2020-12-01T08:11:23 | 2020-12-01T08:11:23 | {} | CONTRIBUTOR |
vuejs | core | 737,018,058 | 2,708 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/11154?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Dependabot will still automatically merge this pull request if you amend it and your tes... | 2020-12-02T06:16:46 | 2020-12-02T06:16:46 | {} | CONTRIBUTOR |
vuejs | core | 737,139,383 | 2,706 | posva | and how did you find the solution?
It's the first time I've seen someone having the issue. If it was from upgrading one of the alphas/betas of Vue, the change was documented in the CHANGELOG and I think that's enough for alphas and betas | 2020-12-02T10:27:56 | 2020-12-02T10:27:56 | {} | MEMBER |
vuejs | core | 737,564,774 | 2,649 | yyx990803 | This seems to be based off incomplete work I was doing in the `postcss-8` branch... note I was waiting on `postcss-modules`'s new release before completing the refactor, and there was a reason why I'm not merging that branch. We also need to coordinate w/ `@vue/cli` before release.
See https://github.com/vuejs/vue-n... | 2020-12-02T23:49:09 | 2020-12-02T23:49:09 | {
"+1": 1,
"eyes": 1
} | MEMBER |
vuejs | core | 735,916,919 | 2,692 | dnlsndr | As far as i can make out, your demo works fine. The "House" SVG is displayed correctly. Am I missing something? | 2020-11-30T17:07:08 | 2020-11-30T17:07:08 | {} | NONE |
vuejs | core | 736,095,085 | 2,648 | yyx990803 | Made some updates:
- `isSVGTag` is a compiler only helper. The original `instanceof SVGElement` check is actually better.
- However, Teleport is technically platform agnostic so we must check for `typeof SVGElement !== 'undefined'` first.
- `ownerSVGElement` is not necessary since all svg elements (not just `<svg>... | 2020-11-30T22:30:15 | 2020-11-30T22:30:15 | {} | MEMBER |
vuejs | core | 736,295,705 | 2,699 | CHOYSEN | I am not sure if i can import a `ref` object from another ".vue" file...
Use `<script setup>`, the template will compile to
```js
import { toDisplayString as _toDisplayString, createVNode as _createVNode, Fragment as _Fragment, openBlock as _openBlock, createBlock as _createBlock } from "/@modules/vue.js"
expor... | 2020-12-01T08:02:48 | 2020-12-01T10:32:11 | {} | CONTRIBUTOR |
vuejs | core | 736,539,123 | 2,597 | luwuer | Thanks for your replying. According to the document, its really a breaking change.
I have aslo a question: If i use a workround class to fix it and its also have to change tests(because a new class has been added on the first frame), is that a breaking change ?
Just like below:
```typescript
onBeforeEnter(... | 2020-12-01T13:05:32 | 2020-12-01T13:10:57 | {} | CONTRIBUTOR |
vuejs | core | 736,591,944 | 2,700 | posva | I agree. I rather have a caveat of not being able to use a `reactive([])` with `v-model` than loose the possibility of computed setters which is one of the most useful features of Vue to deal with data with side effects | 2020-12-01T14:37:32 | 2020-12-01T14:37:32 | {} | MEMBER |
vuejs | core | 736,610,725 | 2,220 | IlCallo | Keywords: typescript augmentation augment globalProperties componentcustomproperties
The guide to add typings is into the typings itself, into `@vue/runtime-core/dist/runtime-core.d.ts`
Search for `ComponentCustomProperties` and `ComponentCustomOptions` declarations and check out the TSDoc
There must be a sectio... | 2020-12-01T15:04:42 | 2020-12-01T15:04:42 | {} | NONE |
vuejs | core | 736,956,810 | 2,097 | zouhangwithsweet | I developed a small tool that allows me to use functions to mount VueComponent.
:biking_man: [vue-create-component](https://github.com/zouhangwithsweet/vue-create-component) | 2020-12-02T03:00:39 | 2020-12-02T03:00:39 | {} | CONTRIBUTOR |
vuejs | core | 737,018,048 | 2,708 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.42 KB (0%) |
| runtime-dom.global.prod.js | 26.73 KB (0%) |
| size-check.global.prod.js | 16.18 KB (0%) | | 2020-12-02T06:16:45 | 2020-12-02T06:16:45 | {} | NONE |
vuejs | core | 737,105,207 | 2,709 | Geekhyt | > > > 可惜
> >
> >
> > 怎么了
>
> 碰巧之前也发现了这个问题
有缘人 | 2020-12-02T09:26:11 | 2020-12-02T09:26:11 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 737,358,591 | 2,435 | yyx990803 | Tested with rebasing on latest `master` and it doesn't really fix #2415 - there's also an easier workaround in vue-router (https://github.com/vuejs/vue-next/issues/2415#issuecomment-737357541) | 2020-12-02T16:53:09 | 2020-12-02T16:53:09 | {} | MEMBER |
vuejs | core | 737,562,741 | 2,710 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.5 KB (0%) |
| runtime-dom.global.prod.js | 26.81 KB (0%) |
| size-check.global.prod.js | 16.18 KB (0%) | | 2020-12-02T23:42:45 | 2020-12-02T23:52:32 | {} | NONE |
vuejs | core | 825,339,846 | 3,577 | zxwild | It definitely looks like a vue-3 bug and should be reopened, I have the same troubles, vue version is `3.0.11`.
Workaround is to register a recursive globally and to give it a **different name**, otherwise it will fail to resolve it.
```javascript
app.component('RecursiveItemWorkaroundComponent', RecursiveItem);
... | 2021-04-23T02:23:47 | 2021-04-23T02:37:50 | {
"+1": 1,
"heart": 1
} | NONE |
vuejs | core | 825,540,849 | 3,645 | hyf0 | The existing code works fine. It's just that if subsequent code makes a change and then forgets to assign a value, hopefully it will report the error at compile time and not have to depend on the test. | 2021-04-23T09:47:59 | 2021-04-23T09:47:59 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 829,118,032 | 3,680 | posva | If you need ComputedGetter, you should justify why you absolutely need it (with words, not just a piece of code).
As for the PR, leave out of it all formatting changes | 2021-04-29T10:28:48 | 2021-04-29T10:28:48 | {} | MEMBER |
vuejs | core | 829,199,431 | 3,691 | mankeheaven | ok,确实
mdn没看到说明
can i use 倒是说的比较明确
希望这个快点标准化吧，哈哈
我程序自己加个polyfill和重定义这个好了 | 2021-04-29T12:32:09 | 2021-04-29T12:32:09 | {} | NONE |
vuejs | core | 825,531,788 | 3,645 | pikax | > type annotation will get a compile error, while type assertion don't
Cast `as ...` is not as good practice, but I don't see the compiler error that you mention, do you mind explaining? The code should be building and passing all the tests regardless of this changes 🤔 | 2021-04-23T09:31:44 | 2021-04-23T09:31:44 | {} | MEMBER |
vuejs | core | 826,118,628 | 3,663 | sapphi-red | This PR does not work.
https://github.com/vuejs/vue/blob/0603ff695d2f41286239298210113cbe2b209e28/src/platforms/web/runtime/components/transition-group.js#L6-L12
| 2021-04-24T16:35:41 | 2021-04-24T16:35:41 | {} | CONTRIBUTOR |
vuejs | core | 826,162,851 | 3,668 | lidlanca |
6. remove console.clear and group logs
| 2021-04-24T22:43:42 | 2021-04-24T22:43:57 | {} | CONTRIBUTOR |
vuejs | core | 828,549,181 | 2,860 | cowills | Should this issue be labelled as a bug instead of a feature? Tree shaking seems like a critical feature for vue 3 given the changes to the global API and the switch from options to composition. | 2021-04-28T15:27:03 | 2021-04-28T15:27:03 | {
"+1": 7,
"eyes": 1
} | NONE |
vuejs | core | 829,156,974 | 1,414 | blabbath | @vuesomedev worked for me, hoewever I had to get rid off one line, otherwise vue-cli wouldn't compile:
```
module.exports = {
chainWebpack: (config) => {
config.module
.rule("vue")
.use("vue-loader")
.tap((options) => {
options.compilerOptions = {
...(options.compilerO... | 2021-04-29T11:38:59 | 2021-04-29T11:38:59 | {
"+1": 5,
"heart": 2
} | NONE |
vuejs | core | 829,979,755 | 2,513 | tungquach | Is there any solution to fix this problem yet? Every time, I mounted an iframe without reloading the page, `@click` handler of element inside iframe won't work anymore | 2021-04-30T09:50:19 | 2021-04-30T09:50:19 | {
"eyes": 1
} | NONE |
vuejs | core | 830,150,216 | 3,693 | pikax | If you add a return to your `computed` it will work without specifying the type.
That is caused by a limitation on typescript, because you are referencing a type that doesn't exist yet with an unknown return type.
```ts
defineComponent({
props: {
title: {
type: String,
required: false,
... | 2021-04-30T14:53:14 | 2021-04-30T14:54:09 | {} | MEMBER |
vuejs | core | 826,068,839 | 3,349 | Akryum | We also have [an entire dedicated section](https://v3.vuejs.org/guide/migration/mount-changes.html) about it in our Migration guide. | 2021-04-24T10:06:24 | 2021-04-24T10:06:24 | {} | MEMBER |
vuejs | core | 826,294,182 | 3,661 | zizyzhang | > I downloaded the codesanbox project you provided, and then:
>
> * update `vue` to `3.0.11`
> * update `@vue/compiler-sfc` to `3.0.11`
> * `yarn build`
>
> I get an error from eslint, then I use `/* eslint-disable */` to disable the error and run `yarn build` again, this time the build is successful.
>
> Ne... | 2021-04-25T09:51:48 | 2021-04-25T09:51:48 | {} | NONE |
vuejs | core | 826,319,400 | 3,668 | lidlanca | @HcySunYang
I opened the issue and put up a demo with all the fixes to the issues I mentioned
to get some feedback and see if there is interest in this kind of changes , before I setup a PR.
SFC playground demo
https://sfc-vue3.netlify.app
- removed console.clear(), and replace with a context group
- ... | 2021-04-25T12:50:56 | 2021-04-25T12:50:56 | {} | CONTRIBUTOR |
vuejs | core | 826,882,612 | 3,678 | 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).
---
Cannot reproduce, you might be attaching the eve... | 2021-04-26T14:31:18 | 2021-04-26T14:31:18 | {} | MEMBER |
vuejs | core | 827,456,170 | 3,683 | ygj6 | @LeeJim
**Change:**
`obj.done = false`
**To:**
`this.items[this.items.length-1].done=false`
can also achieve responsiveness. | 2021-04-27T09:19:55 | 2021-04-27T09:19:55 | {} | MEMBER |
vuejs | core | 828,235,072 | 2,143 | 810505339 | https://codesandbox.io/s/cool-poincare-bftc5?file=/src/views/About.vue | 2021-04-28T07:53:04 | 2021-04-28T07:53:04 | {} | NONE |
vuejs | core | 830,172,292 | 3,693 | pikax | Can you please use the code provided without modifications?
This is really important.
```ts
// prevent `this` from trying to mess with this type
default: () => {
return 'Options API Typing'
}
```
| 2021-04-30T15:24:03 | 2021-04-30T15:24:03 | {} | MEMBER |
vuejs | core | 825,086,794 | 3,653 | LinusBorg | This hasn't anything to do with arrays in particular. The issue is that the template ref function is run inside the render phase, during which you should not have any side-effects that , as that would trigger a re-render.
The same problem would, for example, manifest if you do this:
```html
<template>
<h1> {{ m... | 2021-04-22T18:29:21 | 2021-04-22T18:31:43 | {
"+1": 2
} | MEMBER |
vuejs | core | 825,818,752 | 737 | kharai-tor | 100% agree with @jods4
I think even the `setup` function should not unwrap the returned object props. The fact that there's a difference between these two:
``` vue
<template>
<div>
{{ name }}
</div>
<div>
{{ person.name.value }} <- value ??
</div>
</template>
<script>
export default {
... | 2021-04-23T17:48:30 | 2021-04-23T17:48:30 | {} | NONE |
vuejs | core | 826,045,881 | 3,661 | edison1105 |
1. remove yarn.lock file
2. update `vue `to `3.0.11`
3. update `@vue/compiler-sfc` to `3.0.11`
I'm sure it will work fine and I've tested it locally. | 2021-04-24T06:52:25 | 2021-04-24T06:52:25 | {} | MEMBER |
vuejs | core | 826,646,378 | 3,676 | HcySunYang | See https://v3.vuejs.org/guide/migration/introduction.html#removed-apis
> Users should no longer manually manage the lifecycle of individual Vue components.
Regarding `KeepAlive` cache management, you can track it in https://github.com/vuejs/rfcs/pull/284 | 2021-04-26T08:55:14 | 2021-04-26T08:55:14 | {} | MEMBER |
vuejs | core | 826,794,988 | 3,014 | klevron | Hi, sorry to comment this closed issue but I can't find a way to send props to a custom `defineComponent` function, e.g. :
```ts
import { defineComponent } from 'vue'
export const props = {
msg: {
type: String,
required: true
}
} as const
function customComponent(props: {}) {
return defin... | 2021-04-26T12:27:44 | 2021-04-26T12:56:43 | {} | NONE |
vuejs | core | 827,514,313 | 3,684 | edison1105 | as a workaround:
```javascript
import * as Vue from 'vue'
const unmountKey = Vue.version > '3' ? 'beforeUnmount':'beforeDestroy'
export default {
[unmountKey]() {
console.log(Vue.version)
},
};
``` | 2021-04-27T10:58:02 | 2021-04-27T11:10:20 | {} | MEMBER |
vuejs | core | 825,342,079 | 3,653 | HcySunYang | For this use case:
```html
<div :ref="(el) => arr.push(el) ">
{{ arr.length }}
</div>
```
Because the above code does not work, I'm thinking if users just want to do this, then what is the correct way 🤔 | 2021-04-23T02:30:31 | 2021-04-23T02:30:31 | {} | MEMBER |
vuejs | core | 825,744,460 | 3,001 | nfplee | > You can use single quotes as a workaround:
>
> ```
> <div id="app">
> <list :model="{
> widgets: [
> {
> name: 'Test',
> content: '<strong>Bold Text</strong>' }
> ]
> }"></list>
> </div>
> ```
I have been using this workaround but I have noticed it's messing with... | 2021-04-23T15:40:39 | 2021-04-23T17:30:13 | {} | NONE |
vuejs | core | 789,797,160 | 3,349 | felipec | Great, this "intended" change is not described anywhere and you don't care that the current documentation is wrong.
I guess I'll stay with Vue.js 2 forever, since Vue.js 3 is useless to me.
Thanks. | 2021-03-03T15:27:11 | 2021-04-24T10:01:33 | {} | NONE |
vuejs | core | 826,068,617 | 3,349 | Akryum | [From the docs](https://v3.vuejs.org/api/application-api.html#mount)
> The `innerHTML` of the provided DOM element will be replaced with the rendered template of the application root component. | 2021-04-24T10:04:56 | 2021-04-24T10:04:56 | {} | MEMBER |
vuejs | core | 826,264,043 | 3,661 | HcySunYang | I downloaded the codesanbox project you provided, and then:
- update `vue` to `3.0.11`
- update `@vue/compiler-sfc` to `3.0.11`
- `yarn build`
I get an error from eslint, then I use `/* eslint-disable */` to disable the error and run `yarn build` again, this time the build is successful.
Next, I start a sta... | 2021-04-25T06:04:50 | 2021-04-25T06:04:50 | {} | MEMBER |
vuejs | core | 826,269,403 | 3,668 | HcySunYang | This PR can fix unicode problems https://github.com/vuejs/vue-next/pull/3662 | 2021-04-25T06:52:31 | 2021-04-25T06:52:31 | {} | MEMBER |
vuejs | core | 826,739,660 | 3,674 | wenfangdu | Evan, what do you think? @yyx990803 | 2021-04-26T10:59:41 | 2021-04-26T10:59:41 | {} | NONE |
vuejs | core | 827,515,585 | 3,684 | daybrush | @edison1105
Since there is only default in vue2
```js
import Vue from "vue";
```
It is used as `Vue.version`.
If you use esm, a warning appears. | 2021-04-27T11:00:31 | 2021-04-27T11:00:31 | {} | NONE |
vuejs | core | 828,730,585 | 3,689 | posva | This is expected and you should not combine the composition api with the option api.
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-04-28T19:46:05 | 2021-04-28T19:46:05 | {} | MEMBER |
vuejs | core | 830,176,767 | 3,693 | pikax | ```ts
title: {
type: String,
required: false,
default(this:void) {
return 'Options API Typing'
}
}
``` | 2021-04-30T15:30:50 | 2021-04-30T15:30:50 | {} | MEMBER |
vuejs | core | 826,126,067 | 3,664 | sapphi-red | Seems like it is possible by using `position: absolute`.
[link](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8bGFiZWw+aGlkZSA8aW5wdXQgdHlwZT1cImNoZWNrYm94XCIgdi1tb2RlbD1cImhpZGVcIj48L2xhYmVsPlxuICA8ZGl2PlxuICAgIDxsYWJlbD5pZCA8aW5wdXQgdHlwZT1cInJhZGlvXCIgdmFsdWU9XCJpZFwiIHYtbW9kZWw9XCJzb3J0VHlwZVwiPjwvbG... | 2021-04-24T17:28:46 | 2021-04-24T17:28:46 | {} | CONTRIBUTOR |
vuejs | core | 825,442,783 | 3,654 | LongTengDao | - If `_ctx.fn` can't be falsy (when with modifiers, like Vue 2 did), then remove the condition check in `cacheHandlers: true` edition will be faster;
(code generated in Vue 2, which not allow `fn` to be falsy when with modifiers:)
```js
return _c('div',{
on:{
"click":function($event){
if($event.ta... | 2021-04-23T07:07:48 | 2021-04-23T07:17:41 | {} | CONTRIBUTOR |
vuejs | core | 825,603,476 | 3,659 | Peterosh | thank you , I got it; | 2021-04-23T11:48:06 | 2021-04-23T11:48:06 | {} | NONE |
vuejs | core | 825,826,960 | 3,646 | blayzen-w | Also to add a bit more perspective on the issue, I am rendering the majority of the html on the server and just mounting an app on top with minimal components. This allow things to be mostly intractable until the javascript loads and lowers the content layout shift. The problem is that that the only feed back in this ... | 2021-04-23T18:02:35 | 2021-04-23T18:03:18 | {} | NONE |
vuejs | core | 825,840,240 | 737 | kharai-tor | @yyx990803 This doesn't quite work with object arrays btw. Here's what I mean:
```TS
const item = {
prop: ref('')
};
const array = ref([ item ]);
array.value.push(item); // <- the type checker complains
``` | 2021-04-23T18:24:57 | 2021-04-23T18:24:57 | {} | NONE |
vuejs | core | 826,225,461 | 610 | ljquan | The current version has this problem again | 2021-04-25T02:37:21 | 2021-04-25T02:37:21 | {} | NONE |
vuejs | core | 826,321,695 | 3,668 | HcySunYang | @lidlanca If you have done some excellent work, then there is no doubt that you can make a PR 👍 | 2021-04-25T13:07:52 | 2021-04-25T13:07:52 | {} | MEMBER |
vuejs | core | 828,916,774 | 3,691 | HcySunYang | It's an experimental attribute | 2021-04-29T03:30:07 | 2021-04-29T03:30:07 | {} | MEMBER |
vuejs | core | 825,134,939 | 3,653 | LinusBorg | Without the console.log, your template has no dependency on `arr`. So changing `arr` doesn't cause a re-render.
But when you do the console log ( which happens during the render phase), you access the arr.length, which means, the length of the array is now a dependency of your render function, and changing the arra... | 2021-04-22T19:42:10 | 2021-04-22T21:23:45 | {
"+1": 1
} | MEMBER |
vuejs | core | 825,830,579 | 1,359 | johnsoncodehk | Recent I got some issues direct or indirect point to there, I'm really look forward to see the implement, and this is a great DX improvement.
- https://github.com/johnsoncodehk/volar/discussions/146#discussioncomment-644709
- https://github.com/johnsoncodehk/volar/issues/137
- https://github.com/johnsoncodehk/vola... | 2021-04-23T18:08:36 | 2021-04-23T18:08:36 | {
"+1": 3
} | MEMBER |
vuejs | core | 826,472,769 | 3,631 | lidlanca | @hisland, your code pen does prove that `lzut8.decompress` indeed work for uncompressed base64 string ( by design or by chance I don't know)
however, there is an additional overhead for "empty calculations" before the implementation of `LZUTF8` realize that the input is not compressed and just returned the decoded in... | 2021-04-26T03:15:48 | 2021-04-26T03:16:41 | {} | CONTRIBUTOR |
vuejs | core | 826,653,649 | 3,676 | codon19 | > Regarding `KeepAlive` cache management, you can track it in [vuejs/rfcs#284](https://github.com/vuejs/rfcs/pull/284)
thank you
| 2021-04-26T09:05:02 | 2021-04-26T09:05:02 | {} | NONE |
vuejs | core | 827,382,453 | 3,682 | pikax | > do we need to add some dts test cases for mixins/extends?
Not sure, because it will ignore all the `mixins/extends` the reason is, as soon as we extract the `$props: insfer P` we loose the `Clearable` and `ValueType` generics:
[playground](https://www.typescriptlang.org/play?ts=4.3.0-beta#code/CYUwxgNghgTiAEAz... | 2021-04-27T07:29:58 | 2021-04-27T07:30:10 | {} | MEMBER |
vuejs | core | 827,519,682 | 3,684 | edison1105 | I recommend you to try this https://github.com/vueuse/vue-demi | 2021-04-27T11:03:59 | 2021-04-27T11:03:59 | {} | MEMBER |
vuejs | core | 825,469,304 | 3,654 | HcySunYang | in the `cacheHandlers: false` edition, the falsy value means to remove the event handler, we cannot change this behavior, otherwise, it will be a breaking change. But we can easily make the code more robust, see the latest commit | 2021-04-23T07:52:30 | 2021-04-23T07:52:30 | {
"rocket": 1
} | MEMBER |
vuejs | core | 825,510,737 | 3,655 | HcySunYang | This is intentional, you can check the implementation of isReactive | 2021-04-23T08:56:19 | 2021-04-23T08:56:19 | {} | MEMBER |
vuejs | core | 790,006,450 | 3,349 | LinusBorg | I do care. I just asked you to help a bit by opening an issue in the correct repo, and be a bit more specific about what you said you read in the docs.
If that's too much work for you, feel free to use Vue 2. | 2021-03-03T19:44:18 | 2021-04-24T10:01:41 | {} | MEMBER |
vuejs | core | 826,275,492 | 3,631 | hisland | > @hisland, `lzut8.decompress` expects an lz compressed input, regardless of the encoding . URLs that were generated by `btoa`, when decoded will not be compressed, and the decompressed value is likely to be invalid.
I tried some value works well [codepen sample](https://codepen.io/hisland/pen/dyNgXRo), so I guess... | 2021-04-25T07:41:29 | 2021-04-25T07:41:29 | {} | NONE |
vuejs | core | 826,278,897 | 3,671 | HcySunYang | The onUnmounted hook can only be used inside the setup function | 2021-04-25T08:04:43 | 2021-04-25T08:04:43 | {
"-1": 16,
"eyes": 3
} | MEMBER |
vuejs | core | 826,671,220 | 3,001 | nfplee | > @nfplee
>
> > any idea when this pull request will go live?
>
> I also don't know.
> If you are very anxious, maybe we can try to release a `Knightly build` version via https://github.com/knightly-bot
Thanks but I've just patched this into a custom build. I was more interested in knowing when the pull reque... | 2021-04-26T09:27:09 | 2021-04-26T09:27:09 | {} | NONE |
vuejs | core | 808,946,174 | 3,001 | skirtles-code | *(Responding to a message that has since been deleted)*
I don't think it is a separate problem, it's just another manifestation of the same bug in the decoder.
I believe the fix I proposed would work for both. | 2021-03-28T19:24:33 | 2021-04-28T12:53:08 | {} | CONTRIBUTOR |
vuejs | core | 828,511,769 | 2,600 | kkursor | thanks, @skirtles-code - I've learning Vue and things like this make me cry and want to stop it | 2021-04-28T14:41:02 | 2021-04-28T14:41:02 | {
"laugh": 1
} | NONE |
vuejs | core | 829,250,047 | 3,680 | TakNePoidet | `ComputedGetter` is needed to declare types in the generic `defineComponent` function.
```typescript
interface Computed extends ComputedOptions {
loverTitle: ComputedGetter<string>;
upperTitle: ComputedGetter<string>;
}
export default defineComponent<ComponentPropsOptions<Props>, Props, Data, Computed, Method... | 2021-04-29T13:44:02 | 2021-04-29T13:44:02 | {} | NONE |
vuejs | core | 826,031,555 | 3,660 | HcySunYang | Duplicate of https://github.com/vuejs/vue-next/issues/3393
```js
const nodeExternals = require('webpack-node-externals')
// and
externals: [nodeExternals()],
``` | 2021-04-24T04:19:20 | 2021-04-24T04:19:20 | {} | MEMBER |
vuejs | core | 826,062,242 | 3,349 | LinusBorg | Your issue will not be solved in this repo as the change is an intended one. Vue 3 no longer replaces the element that it mounts to.
So the only thing left to do would be to improve documentation so others don't get the same wrong impression as you did.
From your replies though, it see that you only care about yo... | 2021-04-24T09:09:33 | 2021-04-24T10:01:53 | {} | MEMBER |
vuejs | core | 826,160,824 | 3,668 | lidlanca | 3. making errors less intrusive
opened errors
<img src="https://user-images.githubusercontent.com/8693091/115974269-85aece00-a529-11eb-9741-60ded0786f12.png" width=300/>
minimized errors
<img src="https://user-images.githubusercontent.com/8693091/115974303-a7a85080-a529-11eb-9c25-0b62f2549293.png" width=300/>
... | 2021-04-24T22:19:15 | 2021-04-24T22:44:46 | {} | CONTRIBUTOR |
vuejs | core | 826,248,299 | 3,667 | edison1105 | This is as expected
you should:
```css
<style scoped>
.test ::v-deep(span) {
background: yellow;
}
</style>
``` | 2021-04-25T03:53:17 | 2021-04-25T03:53:26 | {
"+1": 2
} | MEMBER |
vuejs | core | 826,265,182 | 3,667 | HcySunYang | scoped style does not work with manually created DOM elements, if you cannot avoid this situation, then you can use the workaround given by @edison1105 . | 2021-04-25T06:14:33 | 2021-04-25T06:14:33 | {
"+1": 1
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.