start implementing the attributeTypes #9
Annotations
10 errors and 1 warning
Deploy:
resources/js/CustomComponents/MarkDownTextArea.vue#L15
Type '{ updateMarkdown: (markdown: string) => void; }' does not satisfy the constraint 'Record<string, any[]> | ((...args: any[]) => any)'.
|
Deploy:
resources/js/CustomComponents/MarkDownTextArea.vue#L24
Conversion of type 'Event' to type 'HTMLInputElement' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
|
Deploy:
resources/js/CustomComponents/MarkDownTextArea.vue#L24
Property 'target' does not exist on type 'HTMLInputElement'.
|
Deploy:
resources/js/Pages/Attributes/Edit.vue#L68
Property 'error' does not exist on type '{ $: ComponentInternalInstance; $data: {}; $props: Partial<{}> & Omit<{ readonly colors: string[]; readonly attributeType?: { id: number; title: string; description: string; color: string; } | undefined; } & VNodeProps & AllowedComponentProps & ComponentCustomProps & Readonly<...>, never>; ... 10 more ...; $watch<T ...'.
|
Deploy:
resources/js/Pages/Items/Edit.vue#L64
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{ name: string | undefined; description: string; wiring_instructions: string; pros: string; cons: string; hardware_considerations: string; software_considerations: string; example_code: string; }'.
|
Deploy:
resources/js/Pages/Items/Edit.vue#L66
No overload matches this call.
|
Deploy:
resources/js/Pages/Items/Edit.vue#L67
No overload matches this call.
|
Deploy:
resources/js/Pages/Items/Edit.vue#L82
Parameter 'files' implicitly has an 'any' type.
|
Deploy:
resources/js/Pages/Items/Edit.vue#L90
Parameter 'files' implicitly has an 'any' type.
|
Deploy:
resources/js/Pages/Items/Edit.vue#L112
Type 'string | undefined' is not assignable to type 'string'.
|
Deploy
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|