Skip to content

Merge pull request #60 from sreeramyathanda/main #80

Merge pull request #60 from sreeramyathanda/main

Merge pull request #60 from sreeramyathanda/main #80

Triggered via push November 8, 2024 11:22
Status Failure
Total duration 1m 8s
Artifacts

ci.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

22 errors and 13 warnings
format
@amaxa/nextjs#format: command (/home/runner/work/amaxa/amaxa/apps/nextjs) /home/runner/setup-pnpm/node_modules/.bin/pnpm run format --cache --cache-location node_modules/.cache/.prettiercache exited (1)
format
@amaxa/website#format: command (/home/runner/work/amaxa/amaxa/apps/website) /home/runner/setup-pnpm/node_modules/.bin/pnpm run format --cache --cache-location node_modules/.cache/.prettiercache exited (1)
format
Process completed with exit code 1.
typecheck
Type '{ onChange: (...event: any[]) => void; onBlur: Noop; value: string | null | undefined; disabled?: boolean | undefined; name: "image"; ref: RefCallBack; placeholder: string; }' is not assignable to type 'InputProps'.
typecheck
Type '{ status: "Verified" | "Unverified" | "Pending"; id: string; name: string | null; email: string; isPublic: boolean; role: "Admin" | "User"; emailVerified: Date | null; image: string | null; }' is not assignable to type '{ status: "Verified" | "Unverified" | "Pending"; id: string; email: string; isPublic: boolean; role: "Admin" | "User"; name?: string | undefined; image?: string | undefined; }'.
typecheck
Property 'isLoading' does not exist on type 'UseTRPCMutationResult<void, TRPCClientErrorLike<{ input: { description: string; title: string; embedId: string; }; output: void; transformer: true; errorShape: { data: { zodError: typeToFlattenedError<any, string> | null; code: "PARSE_ERROR" | ... 17 more ... | "CLIENT_CLOSED_REQUEST"; httpStatus: number; path?: str...'.
typecheck
Property 'isLoading' does not exist on type 'UseTRPCMutationResult<void, TRPCClientErrorLike<{ input: { description: string; title: string; embedId: string; }; output: void; transformer: true; errorShape: { data: { zodError: typeToFlattenedError<any, string> | null; code: "PARSE_ERROR" | ... 17 more ... | "CLIENT_CLOSED_REQUEST"; httpStatus: number; path?: str...'.
typecheck
@amaxa/nextjs#typecheck: command (/home/runner/work/amaxa/amaxa/apps/nextjs) /home/runner/setup-pnpm/node_modules/.bin/pnpm run typecheck exited (2)
typecheck
Object is possibly 'undefined'.
typecheck
Object is possibly 'undefined'.
typecheck
Object is possibly 'undefined'.
typecheck
Argument of type 'TZDate | undefined' is not assignable to parameter of type 'TZDate'.
typecheck
Process completed with exit code 2.
lint
@amaxa/nextjs#lint: command (/home/runner/work/amaxa/amaxa/apps/nextjs) /home/runner/setup-pnpm/node_modules/.bin/pnpm run lint --cache --cache-location node_modules/.cache/.eslintcache exited (1)
lint: apps/nextjs/src/app/(home)/admin/_components/form.tsx#L40
Use an `interface` instead of a `type`
lint: apps/nextjs/src/app/(home)/admin/_components/form.tsx#L49
Promises must be awaited, end with a call to .catch, end with a call to .then with a rejection handler or be explicitly marked as ignored with the `void` operator
lint: apps/nextjs/src/app/(home)/admin/_components/form.tsx#L54
Promises must be awaited, end with a call to .catch, end with a call to .then with a rejection handler or be explicitly marked as ignored with the `void` operator
lint: apps/nextjs/src/app/(home)/admin/_components/table.tsx#L31
Promises must be awaited, end with a call to .catch, end with a call to .then with a rejection handler or be explicitly marked as ignored with the `void` operator
lint: apps/nextjs/src/components/calendar-full.tsx#L82
Use an `interface` instead of a `type`
lint: apps/nextjs/src/components/calendar-full.tsx#L100
Use an `interface` instead of a `type`
lint: apps/nextjs/src/components/calendar-full.tsx#L108
Use an `interface` instead of a `type`
lint
Process completed with exit code 1.
format
The following actions use a deprecated Node.js version and will be forced to run on node20: pnpm/action-setup@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
typecheck
The following actions use a deprecated Node.js version and will be forced to run on node20: pnpm/action-setup@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
lint
The following actions use a deprecated Node.js version and will be forced to run on node20: pnpm/action-setup@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
lint: apps/website/src/app/(marketing)/about-us/_components/our-partners.tsx#L47
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
lint: apps/website/src/app/(marketing)/about-us/_components/our-partners.tsx#L62
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
lint: apps/website/src/app/(marketing)/team/page.tsx#L89
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
lint: apps/website/src/components/platform-hero.tsx#L48
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
lint: apps/website/src/components/platform-hero.tsx#L53
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
lint: apps/nextjs/src/app/(auth)/unverified/page.tsx#L5
'Button' is defined but never used. Allowed unused vars must match /^_/u
lint: apps/nextjs/src/app/(auth)/unverified/page.tsx#L12
Unnecessary optional chain on a non-nullish value
lint: apps/nextjs/src/app/(auth)/unverified/page.tsx#L12
Unnecessary optional chain on a non-nullish value
lint: apps/nextjs/src/app/(auth)/unverified/page.tsx#L16
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
lint: apps/nextjs/src/app/(auth)/unverified/page.tsx#L41
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