updated fcl #317
Annotations
11 errors and 10 warnings
Tests (20.x)
Process completed with exit code 1.
|
Static checks (20.x):
components/FundAccountForm.tsx#L56
Binding element 'values' implicitly has an 'any' type.
|
Static checks (20.x):
components/FundAccountForm.tsx#L56
Binding element 'isSubmitting' implicitly has an 'any' type.
|
Static checks (20.x):
components/FundAccountSubmitted.tsx#L98
Type 'CadenceArgument<TypeDescriptor<string, { type: string; value: string; }>>' is not assignable to type 'TransactionArg'.
|
Static checks (20.x):
lib/flow/account.ts#L61
Type 'CadenceArgument<TypeDescriptor<string, { type: string; value: string; }>>' is not assignable to type 'TransactionArg'.
|
Static checks (20.x):
lib/flow/account.ts#L62
Type 'CadenceArgument<TypeDescriptor<string | number, { type: string; value: string; }>>' is not assignable to type 'TransactionArg'.
|
Static checks (20.x):
lib/flow/account.ts#L63
Type 'CadenceArgument<TypeDescriptor<string | number, { type: string; value: string; }>>' is not assignable to type 'TransactionArg'.
|
Static checks (20.x):
lib/flow/account.ts#L64
Type 'CadenceArgument<TypeDescriptor<string | number, { type: string; value: string; }>>' is not assignable to type 'TransactionArg'.
|
Static checks (20.x):
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'.
|
Static checks (20.x):
lib/flow/fund.ts#L120
Type 'CadenceArgument<TypeDescriptor<string | number, { type: string; value: string; }>>' is not assignable to type 'TransactionArg'.
|
Static checks (20.x):
lib/flow/fund.ts#L121
Type 'CadenceArgument<TypeDescriptor<string | number, { type: string; value: string; }>>' is not assignable to type 'TransactionArg'.
|
Tests (20.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Tests (20.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Static checks (20.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Static checks (20.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Static checks (20.x):
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
|
Static checks (20.x):
components/LoadingFeedback.tsx#L24
img elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
Static checks (20.x):
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
|
Static checks (20.x):
components/SidebarAccordion.tsx#L142
img elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
Static checks (20.x):
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
|
Static checks (20.x):
pages/api/account.ts#L16
Assign arrow function to a variable before exporting as module default
|