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 | 669,028,543 | 1,782 | haoqunjiang | cc @underfin @yyx990803
The warning comes from runtime-core, should `data-v-` property be an exception to the extra attrs warning?
https://github.com/vuejs/vue-next/blob/v3.0.0-rc.5/packages/runtime-core/src/componentRenderUtils.ts#L153-L160 | 2020-08-05T07:23:29 | 2020-08-05T07:23:29 | {} | MEMBER |
vuejs | core | 669,038,100 | 1,782 | haoqunjiang | Because `Home` in the vite app is a multi-root component, while `Foo` in the jsfiddle is not, add another `div` to the `Foo` template and the warning will appear. | 2020-08-05T07:45:38 | 2020-08-05T07:45:38 | {
"+1": 1
} | MEMBER |
vuejs | core | 669,066,722 | 1,782 | posva | Thanks, I thought the comments had an impact 😅 | 2020-08-05T08:45:47 | 2020-08-05T08:45:47 | {} | MEMBER |
vuejs | core | 669,881,509 | 1,799 | unbyte | > Can you please post the code for the performance test, I am just curious :)
To prevent the optimization from engine affecting the test, I ran tests manually in sections (so I call it simple test).
But for show, I write this simple test, and the result is that my running time is less than half of that
```java... | 2020-08-06T11:52:14 | 2020-08-06T12:10:08 | {} | CONTRIBUTOR |
vuejs | core | 670,037,077 | 1,803 | posva | Please provide a valid repro or context when opening a new issue. I tried locally with the content you provided, and it works | 2020-08-06T16:31:29 | 2020-08-06T16:31:29 | {} | MEMBER |
vuejs | core | 670,443,766 | 1,802 | posva | > I'd really love to see this use-case getting ported over to Vue 3 as it provides so much flexibility.
In that case, it's worth going through the [RFC process](https://github.com/vuejs/rfcs/pulls). I think this belongs in the user land but maybe there is a lot of people using it and it worth adding a utility to Vue... | 2020-08-07T10:14:18 | 2020-08-07T10:14:18 | {
"+1": 3
} | MEMBER |
vuejs | core | 668,245,636 | 1,753 | yyx990803 | A non-extensible object may still be mutable, and can be observed.
Also Vue 2 uses the same `Object.isFrozen` check and Vue 3 should keep it consistent. | 2020-08-03T21:15:43 | 2020-08-03T21:15:43 | {} | MEMBER |
vuejs | core | 668,423,698 | 1,771 | posva | Vue 3 is tree shakeable, you can already benefit from a very light version if you import only what you need.
The compatibility build is not even released yet | 2020-08-04T07:13:09 | 2020-08-04T07:13:09 | {} | MEMBER |
vuejs | core | 668,542,019 | 1,753 | wujieZ | thanks for commented! ! but....
1. when I try to reactive a non-extensible object
```javascript
const { reactive } = Vue
const obj = reactive(Object.preventExtensions({a: 1}))
```
it will cause an error, beacuse a non-extensible object may not be a Frozen obejct, so we try to define a property(__v_reactive) ... | 2020-08-04T11:31:29 | 2020-08-04T13:24:55 | {} | CONTRIBUTOR |
vuejs | core | 668,997,997 | 1,779 | unbyte | Maybe you can try `<script setup>`
See https://github.com/vuejs/rfcs/pull/182 and https://github.com/vuejs/rfcs/blob/sfc-improvements/active-rfcs/0000-sfc-script-setup.md | 2020-08-05T06:01:57 | 2020-08-05T06:04:35 | {} | CONTRIBUTOR |
vuejs | core | 669,135,591 | 1,751 | dependabot-preview[bot] | Superseded by #1783. | 2020-08-05T11:17:59 | 2020-08-05T11:17:59 | {} | CONTRIBUTOR |
vuejs | core | 669,140,605 | 1,772 | 0x009922 | @unbyte I know that `readonly` works deeply. This is the desired behavior, I really need me to pass the map to other parts of the application as read-only. The problem is that nested objects in the map lose their reactivity.
I have prepared [another example on CodePen](https://codepen.io/liquid-solid/pen/eYZYEPd?edito... | 2020-08-05T11:30:31 | 2020-08-05T11:34:37 | {} | NONE |
vuejs | core | 669,219,866 | 1,772 | 0x009922 | @unbyte I think you did not quite understand me. In your example, it goes like this:
```js
// Create some raw object
const test = { some: 'value' };
// Create reactive wrapper of RAW test
const reactiveTest = reactive(test)
// Create readonly wrapper of RAW test
const readonlyTest = readonly(test)
// M... | 2020-08-05T14:17:08 | 2020-08-05T14:17:08 | {} | NONE |
vuejs | core | 669,428,809 | 1,772 | 0x009922 | @unbyte Hmm. I will try to describe my case more precisely. [Here's another example on CodePen](https://codepen.io/liquid-solid/pen/WNwNyqj?editors=1011).
In short, it has the following functions for creating a repository:
```js
function useUnsafeStore() {
const state = reactive({
users: new Map([
... | 2020-08-05T19:20:59 | 2020-08-05T19:20:59 | {} | NONE |
vuejs | core | 669,702,305 | 1,772 | unbyte | I have created a pull request to solve this problem. 😀 | 2020-08-06T05:18:11 | 2020-08-06T06:20:31 | {} | CONTRIBUTOR |
vuejs | core | 669,790,373 | 1,795 | posva | I removed the router from the demo I submitted a PR: https://github.com/xcuiz/vue-next-test/pull/1 | 2020-08-06T08:29:17 | 2020-08-06T08:29:17 | {} | MEMBER |
vuejs | core | 669,926,859 | 1,800 | yyx990803 | This one is tricky because `<select>` relies on specific behavior with its interaction with `<option>` elements inside of it. So it won't work unless you implement your custom `<select>` and `<option>` with the exact same behavior as the native ones (i.e. reflecting options into DOM properties like `.options`, `.select... | 2020-08-06T13:28:42 | 2020-08-06T13:29:02 | {} | MEMBER |
vuejs | core | 669,621,730 | 1,539 | qgates | > What's the point of using render functions inside single file components?
If people could do it in vue 2 they'll continue to do so if it makes sense to them, or they're migrating a vue 2 project | 2020-08-06T01:00:05 | 2020-08-06T14:12:21 | {
"+1": 6
} | NONE |
vuejs | core | 668,534,390 | 1,773 | posva | It should be in the documentation but it's rather intuitive, it would be tedious otherwise. The same happens with `this.$on` when the instance is destroyed.
Closing as this can already be achieved with an easier syntax and such changes should go through the RFC process. | 2020-08-04T11:13:04 | 2020-08-04T11:13:04 | {} | MEMBER |
vuejs | core | 669,097,781 | 1,782 | posva | Transferred here for the discussion even thought it might end up going back | 2020-08-05T09:50:00 | 2020-08-05T09:50:00 | {} | MEMBER |
vuejs | core | 669,471,691 | 1,782 | wheatjs | I'm not sure if you are already aware of this, but from my experience I believe you will need to add `inheritAttrs: false` to the components config. https://jsfiddle.net/b4vjw7er/ Doing so here removes the warning. | 2020-08-05T20:04:59 | 2020-08-05T20:04:59 | {
"-1": 1
} | NONE |
vuejs | core | 669,898,602 | 1,799 | unbyte | > I changed the number of for loops to `10000`, below are the results of several tests(environment: MacBook Pro 16-inch, Chrome 84.0.4147.105):
>
> ```
> a: 4.263916015625ms
> b: 3.35009765625ms
> c: 0.240966796875ms
>
> a: 2.878173828125ms
> b: 3.525146484375ms
> c: 0.202880859375ms
>
> a: 4.864013671875... | 2020-08-06T12:31:41 | 2020-08-06T12:31:41 | {} | CONTRIBUTOR |
vuejs | core | 669,994,319 | 1,802 | posva | There is no global state anymore, see https://github.com/vuejs/rfcs/blob/master/active-rfcs/0009-global-api-change.md#global-api-mapping
But you can could still create custom `createExtendableApp` as a superset of `createApp` that would keep track or registered assets and that exposes an `extend` function that would... | 2020-08-06T15:19:48 | 2020-08-06T15:19:48 | {
"+1": 1
} | MEMBER |
vuejs | core | 670,955,796 | 1,811 | posva | Note updating doesn't directly translate in HTML being patched. | 2020-08-08T17:51:57 | 2020-08-08T17:51:57 | {} | MEMBER |
vuejs | core | 667,559,841 | 1,756 | lucivaldo | I know it doesn't make sense to access or modify a property of the "data" object in the "beforeCreate" hook, but I found this behavior strange. | 2020-08-01T17:01:01 | 2020-08-01T17:01:01 | {} | NONE |
vuejs | core | 667,719,614 | 1,761 | KABBOUCHI | @posva I know that, but my composition lib is using `onMounted`, what if the user call it inside the `onMounted` is there a way to warn them?
Edit: I used `getCurrentInstance` to check if it is mounted.
```js
const vm = getCurrentInstance()
if (vm?.isMounted) {
init()
} else {
onMounted(init)
}
``` | 2020-08-02T20:16:35 | 2020-08-02T20:33:19 | {} | NONE |
vuejs | core | 668,235,188 | 1,763 | yyx990803 | This is expected behavior for `sync` watcher, since atomic updates is what the scheduler is responsible for (and sync watchers are fired without being scheduled).
However `flush: 'pre'` watchers should fire before the component updates, so that is fixed in d4c17fb. | 2020-08-03T20:50:52 | 2020-08-03T20:50:52 | {} | MEMBER |
vuejs | core | 668,976,781 | 1,772 | unbyte | Items from a readonly map will be wrapped with `toReadonly` so it cannot be edit:
https://github.com/vuejs/vue-next/blob/a0e34cee4a09a14548bf1e78f4a82702e9d40717/packages/reactivity/src/collectionHandlers.ts#L255-L268
and in https://composition-api.vuejs.org/api.html#readonly it says
> A readonly proxy is deep: a... | 2020-08-05T04:45:13 | 2020-08-06T05:19:48 | {} | CONTRIBUTOR |
vuejs | core | 669,786,530 | 1,798 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: check-size](https://circleci.com/gh/vuejs/vue-next/7888?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 you... | 2020-08-06T08:21:24 | 2020-08-06T08:21:24 | {} | CONTRIBUTOR |
vuejs | core | 669,903,090 | 1,799 | Picknight | Yep. This is a implementation with good performance but will pollute the prototype. I am not sure this is a good solution. 🧐 | 2020-08-06T12:41:29 | 2020-08-06T12:41:29 | {} | CONTRIBUTOR |
vuejs | core | 670,053,579 | 1,803 | hanx316 | parser test cases of @vue/compiler-core are only for templates
use @vue/compiler-sfc to compile scripts | 2020-08-06T17:00:30 | 2020-08-06T17:02:32 | {} | NONE |
vuejs | core | 671,043,172 | 1,815 | greeeg | It seems related to an issue posted earlier I didn't see #1813. Feel free to close this one if needed. | 2020-08-09T11:58:19 | 2020-08-09T11:58:19 | {} | NONE |
vuejs | core | 666,877,872 | 1,734 | haoqunjiang | So we need to update the `require-v-for-key` for Vue 3 to deal with `template` tags and remove `vue/no-template-key` from `plugin:vue/vue3-essential`, cc @ota-meshi | 2020-07-31T02:29:12 | 2020-07-31T02:29:12 | {
"+1": 1
} | MEMBER |
vuejs | core | 667,968,630 | 1,766 | posva | When specifying the `emits` option, you must list all the emitted events:
```js
emits: ['update:firstName', 'update:lastName'],
``` | 2020-08-03T11:24:52 | 2020-08-03T11:24:52 | {} | MEMBER |
vuejs | core | 668,531,958 | 1,773 | xPaw | Is that documented somewhere? | 2020-08-04T11:07:18 | 2020-08-04T11:07:18 | {} | NONE |
vuejs | core | 669,241,716 | 1,781 | yyx990803 | Fixed in 3692f2738f5b48c5f116d27e2e3b2b571d28a753 | 2020-08-05T14:55:52 | 2020-08-05T14:55:52 | {} | MEMBER |
vuejs | core | 669,178,229 | 1,772 | unbyte | Do you mean that, there are one reactive map and one readonly map pointing to the same raw map, from which you get `item` and `roItem` pointing to the same object, and what you expect is that when you edit `item`, the watcher callback for `roItem` should be triggered (because you can't edit readonly `roItem` directly)?... | 2020-08-05T12:58:53 | 2020-08-06T01:21:53 | {} | CONTRIBUTOR |
vuejs | core | 670,983,211 | 1,813 | posva | It does happen when typing! | 2020-08-08T23:06:08 | 2020-08-08T23:06:08 | {} | MEMBER |
vuejs | core | 670,985,444 | 1,810 | beary | Thanks! It works, I'll create a pull requests to update `jsx.d.ts` | 2020-08-08T23:40:51 | 2020-08-08T23:40:51 | {} | CONTRIBUTOR |
vuejs | core | 711,327,686 | 2,415 | scottasmith | The suggested workaround using the router doesn't work for me. I have updated the original [JSFiddle](https://jsfiddle.net/hauydrxp/4/) and created a [Jist](https://gist.github.com/scottasmith/3a81b510cd79d7c0da0237d4333bad8d) (I was having a few memory leaks at the time console logging the ALL of the hooks from transi... | 2020-10-18T17:45:07 | 2020-10-18T17:47:29 | {} | NONE |
vuejs | core | 711,979,365 | 2,278 | yaquawa | @LinusBorg done https://github.com/vuejs/vue-next/issues/2429 | 2020-10-19T10:10:39 | 2020-10-19T10:11:00 | {} | NONE |
vuejs | core | 712,007,923 | 2,429 | posva | Your reproduction works... | 2020-10-19T10:31:02 | 2020-10-19T10:31:02 | {} | MEMBER |
vuejs | core | 712,050,983 | 2,431 | stowball | Oh wow. Any template does it!
Here's an SFC: https://codepen.io/stowball/pen/MWeeQXK
Here's a UMD build using the app's `innerHTML`: https://codepen.io/stowball/pen/LYZZQmO | 2020-10-19T10:58:40 | 2020-10-19T10:58:40 | {} | NONE |
vuejs | core | 712,290,284 | 2,437 | yyx990803 | In v3 there really isn't the concept of "abstract" components (i.e. ones that are omitted from parent chains) anymore, so this is expected behavior (and yes, technically a breaking change from v2, but the idea is that the usage of `$parent` should be strongly discouraged in v3 with Composition APIs)
I think the actu... | 2020-10-19T16:41:09 | 2020-10-19T16:43:14 | {
"confused": 1
} | MEMBER |
vuejs | core | 712,395,678 | 2,437 | yyx990803 | You are using `$parent` which is a special getter on the public proxy, not `instance.parent` on the internal instance.
The internal `.parent` chain works (and includes functional components), but there is no equivalent in v2. The problematic part is the `.$parent` chain on the public instance which currently has a d... | 2020-10-19T19:34:04 | 2020-10-19T19:35:39 | {} | MEMBER |
vuejs | core | 712,662,297 | 2,440 | 07akioni | directive hook is not called in render phase, so vue doesn't know it is related to the component rendering | 2020-10-20T07:46:02 | 2020-10-20T07:49:44 | {} | CONTRIBUTOR |
vuejs | core | 712,664,751 | 2,440 | murongg | @07akioni thank you,learn a lot from you | 2020-10-20T07:50:33 | 2020-10-20T07:50:33 | {
"laugh": 1
} | NONE |
vuejs | core | 712,992,118 | 2,448 | AaronBank | ### Add reproduction link
https://github.com/AaronBank/vue-next/commit/312daa498b1b605d5bda20a1e423d231fba164f7 | 2020-10-20T16:38:54 | 2020-10-20T16:38:54 | {} | NONE |
vuejs | core | 713,035,266 | 2,313 | yyx990803 | Thanks for the PR - however, this is not the right file to place the declaration. (`global.d.ts` is for source code only). Also, this may not be needed in all cases (see https://github.com/vitejs/create-vite-app/pull/17#issuecomment-707447288) | 2020-10-20T17:54:56 | 2020-10-20T17:54:56 | {
"+1": 1
} | MEMBER |
vuejs | core | 713,360,554 | 2,429 | yaquawa | @LinusBorg @07akioni @posva can you guys confirm it's working on the iife version of vue >=3.0.1 ? | 2020-10-21T07:12:06 | 2020-10-21T07:12:06 | {} | NONE |
vuejs | core | 713,880,322 | 2,381 | LinusBorg | I'll reopen this so we can re-evaluate, thanks so far. | 2020-10-21T21:12:06 | 2020-10-21T21:12:06 | {} | MEMBER |
vuejs | core | 714,075,516 | 2,455 | edison1105 | incorrect reproduction link @HrishikeshKarale | 2020-10-22T00:42:57 | 2020-10-22T00:42:57 | {} | MEMBER |
vuejs | core | 712,286,152 | 2,431 | yyx990803 | This is an intended change. v3 uses the equivalent of v2's `whitespace: 'condense'` in all cases, so whitespace between tags are only preserved if it contains no newlines:
```html
<div>
<span>{{ foo }}</span> <span>{{ baz }}</span>
</div>
```
See https://github.com/vuejs/vue/tree/dev/packages/vue-template-c... | 2020-10-19T16:33:41 | 2020-10-19T16:33:41 | {
"-1": 9
} | MEMBER |
vuejs | core | 712,660,302 | 2,440 | murongg | > Another solution:
>
> ```
> <div v-lazy="{ src: errorlazy.src }" />
> ```
thank you,but this operation is very troublesome | 2020-10-20T07:42:22 | 2020-10-20T07:42:22 | {} | NONE |
vuejs | core | 713,268,249 | 2,424 | 69hunter | Hi @logaretm, this fix is to align the behavior of provide/inject in composition API with options API (which is the same in Vue 2) | 2020-10-21T03:15:08 | 2020-10-21T03:15:08 | {} | CONTRIBUTOR |
vuejs | core | 713,341,455 | 2,452 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-21T06:31:11 | 2020-10-21T06:31:11 | {} | NONE |
vuejs | core | 714,410,741 | 2,389 | basvanmeurs | @antfu
This occurred to me as well, but..
computed.cleanup is different from watch stopHandles, and even effectScope.stop.
When running a stop on a watcher, it makes the **effect** inactive: it sets `effect.active` to `false`. It's really destroyed and can no longer be used.
In case of computed.cleanup it ... | 2020-10-22T10:54:02 | 2020-10-22T11:00:45 | {} | CONTRIBUTOR |
vuejs | core | 712,446,141 | 2,338 | yyx990803 | @JensD98 please open a separate issue since it's a different problem. | 2020-10-19T21:14:39 | 2020-10-19T21:14:39 | {} | MEMBER |
vuejs | core | 712,567,097 | 2,427 | javie5 | @yyx990803 可以请教下为什么以下2种情况使用for in 视图依然可以同步更新吗:
1.在computed 中使用for in时,同时使用array.length
2.不使用数组,改用对象(初始化为空白对象)
![image](https://user-images.githubusercontent.com/10527883/96537140-2943cb00-12c8-11eb-97fc... | 2020-10-20T03:35:19 | 2020-10-20T03:35:19 | {} | NONE |
vuejs | core | 712,631,236 | 2,443 | HcySunYang | Please check your console:
```
vue.js:1174 [Vue warn]: Component inside <Transition> renders non-element root node that cannot be animated.
at <PageA onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< null > >
at <KeepAlive include="PageA,PageB" >
at <BaseTransition mode="out-in" appear=false persisted=fals... | 2020-10-20T06:43:50 | 2020-10-20T06:43:50 | {
"+1": 1
} | MEMBER |
vuejs | core | 712,739,981 | 2,446 | 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). | 2020-10-20T10:01:43 | 2020-10-20T10:01:43 | {} | MEMBER |
vuejs | core | 713,109,520 | 2,350 | yyx990803 | @LeBenLeBen the types should reflect it, but you can share props definitions by simply spreading them. | 2020-10-20T20:08:39 | 2020-10-20T20:08:39 | {
"+1": 1
} | MEMBER |
vuejs | core | 709,590,783 | 2,381 | LinusBorg | Not sure If you misunderstood my intentions.
1. I'm saying the watch is removed for you.
2. Still it should not throw an error when called again, hence I said (we should still take a look)
3. We could not reproduce the behavior in a clean example. here's another jsfiddle:
https://jsfiddle.net/85geva61/
We ca... | 2020-10-15T21:07:27 | 2020-10-21T21:09:21 | {} | MEMBER |
vuejs | core | 714,362,547 | 2,456 | posva | You can find more info in existing issues like https://github.com/vuejs/vue-next/issues/1706
https://github.com/vuejs/vue-next/issues?q=is%3Aissue+sort%3Aupdated-desc+watch+post+is%3Aclosed | 2020-10-22T09:29:34 | 2020-10-22T09:29:34 | {} | MEMBER |
vuejs | core | 712,075,232 | 2,431 | posva | Related: https://github.com/vuejs/vue-next/pull/1600 | 2020-10-19T11:13:57 | 2020-10-19T11:13:57 | {} | MEMBER |
vuejs | core | 712,634,083 | 2,443 | posva | Your pages must have one root node if you want to use them inside transitions
---
> So I can only come here to ask questions
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2020-10-20T06:50:29 | 2020-10-20T06:50:29 | {} | MEMBER |
vuejs | core | 712,658,865 | 2,440 | 07akioni | Another solution:
```html
<div v-lazy="{ src: errorlazy.src }" />
``` | 2020-10-20T07:39:35 | 2020-10-20T07:39:35 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 713,292,080 | 2,450 | unbyte | as a workaround, capitalize component name `<Test name="Broken component"> This content shouldn't be showing up </Test>` | 2020-10-21T04:23:01 | 2020-10-21T04:25:41 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 713,580,672 | 2,424 | logaretm | @69hunter I understand, no worries. I just always viewed this as a feature especially I would imagine `provide/inject` would be used primarily with the composition API. I wasn't aware it caused issues with the options API or assumed that's expected.
I patched my code to use self-injections with `getCurrentInstance` ... | 2020-10-21T13:35:25 | 2020-10-21T13:53:45 | {} | NONE |
vuejs | core | 714,765,290 | 2,466 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-22T21:12:41 | 2020-10-22T21:12:41 | {} | NONE |
vuejs | core | 714,839,777 | 2,389 | antfu | I misunderstood the original motivation, thanks for the detailed explanation. The naming is good to me then 👍 | 2020-10-23T00:47:58 | 2020-10-23T00:48:12 | {} | MEMBER |
vuejs | core | 712,013,397 | 2,429 | yaquawa | @posva have you clicked the "Hello Vue 3 in CodeSandbox!" ? If it works, the alert should appears. | 2020-10-19T10:34:33 | 2020-10-19T10:34:47 | {} | NONE |
vuejs | core | 712,424,446 | 2,431 | stowball | I would have to say that this is a bad change. Many teams, mine included, use new lines exclusively between tags, including those in "sentences".
This change basically breaks many of our layouts where, for example, we intentionally bold words besides hyperlinks.
It is reasonable to expect that the compiled templa... | 2020-10-19T20:30:47 | 2020-10-19T20:30:47 | {
"+1": 8
} | NONE |
vuejs | core | 712,440,809 | 2,437 | LinusBorg | I know. `$parent` is using instance.parent.proxy.
But that fails when a BaseTransition is the parent. | 2020-10-19T21:03:42 | 2020-10-19T21:03:42 | {} | MEMBER |
vuejs | core | 712,658,153 | 2,440 | LinusBorg | The component doesn't re-render because the only reactive dependency of the template - `errorlazy` did not change. `errorlazy.src` did change, but that property is not a dependency of the component.
So neither the component's nor the directive's `updated()` hook runs, and that's expected.
you can however use i.e ... | 2020-10-20T07:38:10 | 2020-10-20T07:38:10 | {} | MEMBER |
vuejs | core | 712,891,835 | 2,445 | unbyte | I'm doubt about if the associated issue is a bug, because there is a problem with the code itself.
```vue
const block = Vue.ref({id:1});
// ...
<my-test v-for="id in [block.id]" :key="id" />
```
when `block.value` is null, `[block.value.id]` should not work.
---
a more appropriate sample works well: http... | 2020-10-20T14:24:39 | 2020-10-20T14:30:59 | {} | CONTRIBUTOR |
vuejs | core | 713,463,119 | 2,429 | ttntm | > This works correctly in a reproduction using 3.0.1 global build (https://jsfiddle.net/yyx990803/3scy68d5/1/) and also works on a fresh vue-cli project using 3.0.1. There could be a compiler/runtime version mismatch in your project that doesn't properly camelize the event when emitting (make sure your `@vue/compiler-s... | 2020-10-21T10:12:33 | 2020-10-21T10:12:33 | {
"+1": 2
} | NONE |
vuejs | core | 711,953,146 | 2,278 | LinusBorg | Please open a bug. Commments on merged commits get lost quickly. | 2020-10-19T09:50:11 | 2020-10-19T09:50:11 | {} | MEMBER |
vuejs | core | 712,110,566 | 2,434 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 39.97 KB (0%) |
| runtime-dom.global.prod.js | 26.3 KB (0%) |
| size-check.global.prod.js | 15.8 KB (0%) | | 2020-10-19T12:04:42 | 2020-10-19T12:04:42 | {} | NONE |
vuejs | core | 712,143,696 | 2,427 | edison1105 | @posva It's relate to `for in `, not `for of`. | 2020-10-19T13:07:19 | 2020-10-19T13:07:19 | {} | MEMBER |
vuejs | core | 712,524,999 | 2,429 | yyx990803 | This works correctly in a reproduction using 3.0.1 global build (https://jsfiddle.net/yyx990803/3scy68d5/1/) and also works on a fresh vue-cli project using 3.0.1. There could be a compiler/runtime version mismatch in your project that doesn't properly camelize the event when emitting (make sure your `@vue/compiler-sfc... | 2020-10-20T01:05:18 | 2020-10-20T01:09:26 | {
"+1": 2
} | MEMBER |
vuejs | core | 712,847,172 | 906 | posva | @gregg-cbs you were maybe on the old docs. The ones for vue-router for Vue 3 are at https://next.router.vuejs.org/guide/advanced/transitions.html#transitions | 2020-10-20T13:24:01 | 2020-10-20T13:24:01 | {} | MEMBER |
vuejs | core | 714,765,165 | 2,465 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-22T21:12:26 | 2020-10-22T21:12:26 | {} | NONE |
vuejs | core | 711,505,790 | 2,423 | Alanscut | Are you using IE browser? I get the button with `Button Text` content when runing your code with chrome browser, but get nothing with IE browser. | 2020-10-19T04:04:22 | 2020-10-19T04:04:22 | {} | CONTRIBUTOR |
vuejs | core | 712,048,826 | 2,429 | LinusBorg | @posva I don't get any alert from clicking on HelloWorld's body, can't say this works. | 2020-10-19T10:57:20 | 2020-10-19T10:57:30 | {} | MEMBER |
vuejs | core | 712,389,224 | 2,429 | 07akioni | Docs may need an update too.
 | 2020-10-19T19:20:35 | 2020-10-19T19:20:35 | {} | CONTRIBUTOR |
vuejs | core | 714,280,739 | 2,456 | Jokcy | is there any side effects if we `flushJobs` when `pendingPreFlushCbs.length > 0`
```
if (queue.length || pendingPostFlushCbs.length || pendingPreFlushCbs.length) {
flushJobs(seen)
}
```
this code passed all test | 2020-10-22T07:07:02 | 2020-10-22T07:42:33 | {} | CONTRIBUTOR |
vuejs | core | 711,648,616 | 2,420 | LinusBorg | > In vue 2 it would try everything if it has ||, now it throws error
That's simply not the case. Your javascript expression `tag.translations[0].translation` will throw that error in Vue 2 and Vue 3. `||` is just the OR operator, not a magic error handler. | 2020-10-19T06:28:45 | 2020-10-19T06:28:45 | {} | MEMBER |
vuejs | core | 711,941,544 | 2,278 | yaquawa | Hi there, I found my code suddenly didn't work after this merge :
```
<foo @my-event-name="callEvent" />
```
```
this.$emit('my-event-name') // `callEvent` not triggered
```
would you please fix this issue ? | 2020-10-19T09:42:54 | 2020-10-19T09:50:15 | {} | NONE |
vuejs | core | 712,171,182 | 2,423 | KaelWD | https://github.com/vuejs/rfcs/blob/master/active-rfcs/0008-render-function-api-change.md#reliance-on-vue-core
I don't know if there's any documentation on this yet, see https://github.com/vuetifyjs/vuetify/discussions/4068#discussioncomment-24984 | 2020-10-19T13:51:56 | 2020-10-19T13:52:21 | {} | CONTRIBUTOR |
vuejs | core | 712,474,786 | 2,433 | yyx990803 | You error probably is due to your `tsc` being a global installation of an older version of TS.
Also, the `tsconfig.json` is used by the CLI and won't work with a plain `tsc` anyway, since it doesn't know how to handle `*.vue` files. | 2020-10-19T22:22:43 | 2020-10-19T22:22:43 | {} | MEMBER |
vuejs | core | 712,372,357 | 2,427 | 07akioni | <del>Currently in JS there is no trap for `for in` in Proxy. So it may not be consider as a bug but rather a constraint of JS.
[https://stackoverflow.com/questions/38586471/how-to-control-property-enumeration-for-in-with-proxy-objects](https://stackoverflow.com/questions/38586471/how-to-control-property-enumeration-... | 2020-10-19T18:49:21 | 2020-10-20T01:27:27 | {} | CONTRIBUTOR |
vuejs | core | 712,655,006 | 2,444 | basvanmeurs | Excuse me. I've updated the example | 2020-10-20T07:32:02 | 2020-10-20T07:32:02 | {} | CONTRIBUTOR |
vuejs | core | 712,829,052 | 906 | gregg-cbs | The css as per the docs is now incorrect for V3 transitions.
So anyone who is coming here who has copied the fade css from the docs, **here is the updated code:**
```html
<router-view v-slot="{ Component }">
<transition name="fade" mode="out-in">
<component :is="Component"></component>
</transit... | 2020-10-20T12:56:26 | 2020-10-20T12:56:26 | {
"+1": 6
} | NONE |
vuejs | core | 711,394,333 | 906 | wiseadme | Hi! How I can add a transition tag in the render function? It works fine in the Vue-2. But it doesn't work in Vue-3
setup() {
...
...
return () => h('transition', {name: 'fade'}, [VNode])
}
It creates the transition tag in DOM | 2020-10-18T19:15:09 | 2020-10-18T19:20:43 | {} | NONE |
vuejs | core | 712,443,271 | 2,394 | yyx990803 | Thanks for the PR... but in my opinion this isn't really needed, since the unused args will be removed by minifiers in production builds anyway, so it's better to avoid extra complexity in the Vue compiler. | 2020-10-19T21:08:41 | 2020-10-19T21:08:41 | {
"+1": 1
} | MEMBER |
vuejs | core | 712,520,340 | 2,437 | yyx990803 | That's why I'm suggesting the fix is going further up the parent chain when `$parent` encounters a functional component (i.e. an internal instance whose `proxy` is `null`). | 2020-10-20T00:48:55 | 2020-10-20T00:48:55 | {} | MEMBER |
vuejs | core | 712,530,046 | 2,438 | IrvingZhao | 在npmjs.org中，查找vue-template-compiler时，发现vue-template-compiler最高版本只有2.6.12 | 2020-10-20T01:23:50 | 2020-10-20T01:23:50 | {} | NONE |
vuejs | core | 712,663,796 | 2,440 | 07akioni | technically it is possible to make every prop change of a reactive object cause re-rendering. but it is not efficient. For example:
```
render () {
return reactive.a
}
reactive.b = 'c' // it'd better not cause re-rendering
``` | 2020-10-20T07:48:43 | 2020-10-20T07:48:43 | {} | CONTRIBUTOR |
vuejs | core | 714,265,566 | 2,389 | antfu | This is indeed a good addition. However, I am a bit concern about the constancy of the APIs we are going to have.
## Currently & On Going
To clean up effects:
### Effect
```ts
import { stop, effect } from '@vue/reactivity'
const runner = effect(/* ... */)
stop(runner)
```
### Watch / Watch Effect... | 2020-10-22T06:34:38 | 2020-10-22T06:34:38 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.