ignore lint errors #330
Annotations
10 errors and 7 warnings
Run npm run tsc:
components/FundAccountForm.tsx#L56
Binding element 'values' implicitly has an 'any' type.
|
Run npm run tsc:
components/FundAccountForm.tsx#L56
Binding element 'isSubmitting' implicitly has an 'any' type.
|
Run npm run tsc:
components/FundAccountSubmitted.tsx#L96
Type 'CadenceArgument<TypeDescriptor<string, { type: string; value: string; }>>' is not assignable to type 'TransactionArg'.
|
Run npm run tsc:
lib/flow/account.ts#L61
Type 'CadenceArgument<TypeDescriptor<string, { type: string; value: string; }>>' is not assignable to type 'TransactionArg'.
|
Run npm run tsc:
lib/flow/account.ts#L62
Type 'CadenceArgument<TypeDescriptor<string | number, { type: string; value: string; }>>' is not assignable to type 'TransactionArg'.
|
Run npm run tsc:
lib/flow/account.ts#L63
Type 'CadenceArgument<TypeDescriptor<string | number, { type: string; value: string; }>>' is not assignable to type 'TransactionArg'.
|
Run npm run tsc:
lib/flow/account.ts#L64
Type 'CadenceArgument<TypeDescriptor<string | number, { type: string; value: string; }>>' is not assignable to type 'TransactionArg'.
|
Run npm run tsc:
lib/flow/fund.ts#L111
Type 'CadenceArgument<TypeDescriptor<{ fields: { name: string; value: (string | number)[]; }[]; }, { type: string; value: { id: string; fields: { name: string; value: JsonCdc<string, unknown>; }[]; }; }>>' is not assignable to type 'TransactionArg'.
|
Run npm run tsc:
lib/flow/fund.ts#L120
Type 'CadenceArgument<TypeDescriptor<string | number, { type: string; value: string; }>>' is not assignable to type 'TransactionArg'.
|
Run npm run tsc:
lib/flow/fund.ts#L121
Type 'CadenceArgument<TypeDescriptor<string | number, { type: string; value: string; }>>' is not assignable to type 'TransactionArg'.
|
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Run npm run lint:
components/Header.tsx#L32
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
Run npm run lint:
components/LoadingFeedback.tsx#L24
img elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
Run npm run lint:
components/LoadingFeedback.tsx#L24
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
Run npm run lint:
components/SidebarAccordion.tsx#L142
img elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
Run npm run lint:
components/SidebarAccordion.tsx#L142
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
Run npm run lint:
pages/api/account.ts#L16
Assign arrow function to a variable before exporting as module default
|
Loading