Skip to content

fix: allow data with the same name as components #5146

fix: allow data with the same name as components

fix: allow data with the same name as components #5146

Triggered via pull request December 6, 2023 11:54
Status Failure
Total duration 1m 18s
Artifacts

test.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

7 errors
build (16, ubuntu-latest)
Property 'foo' does not exist on type 'Vue3Instance<{}, Readonly<ExtractPropTypes<{}>>, Readonly<ExtractPropTypes<{}>>, {}, {}, true, ComponentOptionsBase<any, any, any, any, ... 5 more ..., any>> & ... 4 more ... & Readonly<...>'.
build (16, ubuntu-latest)
Property 'foo' does not exist on type '{ $: ComponentInternalInstance; $data: {}; $props: Partial<{}> & Omit<{} & VNodeProps & AllowedComponentProps & ComponentCustomProps & Readonly<...>, never>; ... 10 more ...; $watch<T extends string | ((...args: any) => any)>(source: T, cb: T extends (...args: any) => infer R ? (args_0: R, args_1: R) => any : (...ar...'.
build (16, ubuntu-latest)
Process completed with exit code 1.
build (16, windows-latest)
The job was canceled because "_16_ubuntu-latest" failed.
build (16, windows-latest)
The operation was canceled.
build (16, macos-latest)
The job was canceled because "_16_ubuntu-latest" failed.
build (16, macos-latest)
The operation was canceled.