57 image scroping in inscription form image upload error management by YoungMame · Pull Request #59 · YoungMame/matcha

YoungMame · 2025-12-01T13:17:19Z

Basic profile settings page

Image upload scrop, zoom, rotate on unboarding

Image Scropper component

Copilot

Pull request overview

This PR implements image cropping, zoom, and rotation functionality for the onboarding inscription form with improved error management. The changes enable users to customize their uploaded images before submission.

Key Changes

Added react-easy-crop library for interactive image cropping with zoom and rotation controls
Implemented crop/rotation settings storage in onboarding data structure
Extended backend API to accept and process crop/rotation parameters using Sharp
Updated gender values from male/female to men/women across frontend and backend

Reviewed changes

Copilot reviewed 36 out of 38 changed files in this pull request and generated 26 comments.

Show a summary per file

File	Description
nextjs/matcha/src/utils/cropImage.ts	New utility for client-side image cropping with canvas manipulation
nextjs/matcha/src/utils/getImageUrl.ts	Helper to create blob URLs from File objects
nextjs/matcha/src/components/common/ImageCropper.tsx	New cropper component with zoom and rotation controls
nextjs/matcha/src/components/onboarding/steps/PicturesStep.tsx	Enhanced picture upload step with cropping UI integration
nextjs/matcha/src/hooks/useOnboarding.ts	Updated to handle crop/rotation settings submission
nextjs/matcha/src/types/onboarding.ts	Added crop and rotation settings to onboarding data type
nextjs/matcha/src/mocks/browsing_mocks.ts	Updated gender values to use new men/women convention
nextjs/matcha/src/contexts/MeContext.tsx	New context provider for user profile data management
nextjs/matcha/src/app/(logged)/me/page.tsx	New profile settings page for viewing/editing user data
fastify/assets/srcs/controllers/private/me/profilePictures.ts	Enhanced to process crop/rotation with Sharp library
fastify/assets/srcs/plugins/checkImageConformity.ts	Updated validation to support crop dimensions
fastify/assets/srcs/services/UserService.ts	Added firstName/lastName to profile responses
package.json	Added react-easy-crop and react-image-crop dependencies

Files not reviewed (1)

nextjs/matcha/pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (3)

nextjs/matcha/src/components/onboarding/steps/PicturesStep.tsx:199

Using == instead of === for comparison. In JavaScript/TypeScript, it's best practice to use strict equality (===) to avoid type coercion issues.

			const picture = currentCroppingIndex == 0 ? profilePicture : additionalPictures[currentCroppingIndex - 1];

nextjs/matcha/src/app/(logged)/me/page.tsx:11

Unused function onChange.

function onChange(field: string, value: any) {

nextjs/matcha/src/hooks/useOnboarding.ts:4

Unused import Fira_Sans_Extra_Condensed.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-12-01T13:22:39Z

+        const heightensAgo = today.setFullYear(today.getFullYear() - 18);
+
+        if (heightensAgo - (me.birthdate as Date).getTime() < 0)


Typo in variable name: heightensAgo should be eighteenYearsAgo to correctly represent "18 years ago".

Suggested change

const heightensAgo = today.setFullYear(today.getFullYear() - 18);

if (heightensAgo - (me.birthdate as Date).getTime() < 0)

const eighteenYearsAgo = today.setFullYear(today.getFullYear() - 18);

if (eighteenYearsAgo - (me.birthdate as Date).getTime() < 0)

Copilot · 2025-12-01T13:22:39Z

+  { value: "heterosexual", label: "Hétérosexuel" },
+  { value: "homosexual", label: "Homosexuel" },
+  { value: "bisexual", label: "Bisexuel" },
+]


Missing semicolon at the end of the ORIENTATION_OPTIONS array declaration.

Copilot · 2025-12-01T13:22:39Z

+                onClick={() => setRotation((rotation + 90) % 180)}
+                size="small"
+                aria-label="Rotate right"
+            >
+                <div>\-</div>
+            </IconButton>
+            <IconButton
+                onClick={() => setRotation((rotation + 90) % 180)}


The rotation button handlers both use the same logic (rotation + 90) % 180, which will cause both buttons to rotate in the same direction. Additionally, the modulo 180 means rotations will jump from 90° to -90° instead of completing a full rotation. Consider:

Using (rotation - 90) % 360 for one button and (rotation + 90) % 360 for the other

Or using different increment/decrement values to differentiate the buttons' behavior

Suggested change

onClick={() => setRotation((rotation + 90) % 180)}

size="small"

aria-label="Rotate right"

>

<div>\-</div>

</IconButton>

<IconButton

onClick={() => setRotation((rotation + 90) % 180)}

onClick={() => setRotation((rotation - 90 + 360) % 360)}

size="small"

aria-label="Rotate left"

>

<div>\-</div>

</IconButton>

<IconButton

onClick={() => setRotation((rotation + 90) % 360)}

Copilot · 2025-12-01T13:22:40Z

+  );
+}
+
+export function useMe() {


Debug console.log statements should be removed from production code.

Copilot · 2025-12-01T13:22:40Z

+function onChange(field: string, value: any) {
+    console.log(`Field ${field} changed to`, value);
+}


The function onChange on lines 11-13 is defined but never used. Consider removing it or implementing its functionality if it was meant to be used in the form fields.

Suggested change

function onChange(field: string, value: any) {

console.log(`Field ${field} changed to`, value);

}

Copilot · 2025-12-01T13:22:44Z

+	crop: Area;
+}
+
+const CROP_AREA_ASPECT = 9 / 16;


Unused variable CROP_AREA_ASPECT.

Suggested change

const CROP_AREA_ASPECT = 9 / 16;

Copilot · 2025-12-01T13:22:45Z

+
+import { createContext, useContext, ReactNode, useState, useEffect } from "react";
+import { Location } from "../types/location";
+import axios, { Axios } from "axios";


Unused import Axios.

Copilot · 2025-12-01T13:22:45Z

+                let rotation = Number((request.body as { rotation?: { value: string } }).rotation?.value) || 0;
+                if (rotation > 180) rotation = 180;
+                if (rotation < -180) rotation = -180;


The value assigned to rotation here is unused.

Suggested change

let rotation = Number((request.body as { rotation?: { value: string } }).rotation?.value) || 0;

if (rotation > 180) rotation = 180;

if (rotation < -180) rotation = -180;

Copilot · 2025-12-01T13:22:45Z

+
+	const onCropComplete = (croppedArea: Area, croppedAreaPixels: Area) => {
+		setCroppedAreaPixels(croppedAreaPixels)
+	}


Avoid automated semicolon insertion (91% of all statements in the enclosing function have an explicit semicolon).

Suggested change

}

};

Copilot · 2025-12-01T13:22:45Z

+			setRotation(0);
+			setZoom(1);
+		} catch (e) {
+			console.error(e)


Avoid automated semicolon insertion (91% of all statements in the enclosing function have an explicit semicolon).

Suggested change

console.error(e)

console.error(e);

…upload-error-management

* Initial plan * Fix image rotation to use 360 degrees instead of 180 Co-authored-by: YoungMame <134452452+YoungMame@users.noreply.github.com> * Remove package-lock.json from tracking Co-authored-by: YoungMame <134452452+YoungMame@users.noreply.github.com> * Address code review feedback: use strict equality, proper types, and rotation icons Co-authored-by: YoungMame <134452452+YoungMame@users.noreply.github.com> * Remove npm package-lock.json (project uses pnpm) Co-authored-by: YoungMame <134452452+YoungMame@users.noreply.github.com> * Extract image selection logic and add configurable output format Co-authored-by: YoungMame <134452452+YoungMame@users.noreply.github.com> * Restore original package-lock.json from main branch Co-authored-by: YoungMame <134452452+YoungMame@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: YoungMame <134452452+YoungMame@users.noreply.github.com> Co-authored-by: ValentinMalassigne <valentin.malassigne3@gmail.com>

Copilot

Pull request overview

Copilot reviewed 34 out of 37 changed files in this pull request and generated 16 comments.

Files not reviewed (1)

nextjs/matcha/pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (3)

nextjs/matcha/src/hooks/useOnboarding.ts:5

Unused import Fira_Sans_Extra_Condensed.
fastify/assets/srcs/routes/private/user/me/profile.ts:64
This property is overwritten by another property in the same object literal.

						firstName: { type: 'string' },

fastify/assets/srcs/routes/private/user/me/profile.ts:65

This property is overwritten by another property in the same object literal.

						lastName: { type: 'string' },

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-12-18T06:32:17Z

 						firstName: { type: 'string' },
 						lastName: { type: 'string' },


Duplicate property definitions for 'firstName' and 'lastName' in the schema. Lines 64-65 duplicate lines 67-68, which will cause validation issues.

Suggested change

firstName: { type: 'string' },

lastName: { type: 'string' },

Copilot · 2025-12-18T06:32:18Z

 ];

-const MALE_PICTURES = [
+const men_PICTURES = [


Inconsistent naming convention: 'men_PICTURES' mixes snake_case with UPPER_CASE. Should be either 'MALE_PICTURES' or 'menPictures' to match the codebase style.

Copilot · 2025-12-18T06:32:18Z

+                // console.log('width', width);
+                // console.log('width > maxWidth', width > maxWidth);
+                // console.log('width < minWidth', width < minWidth);
+                // console.log(ratio)
+                // console.log(expectedRatio)


Commented out console.log statements should be removed rather than left in the code. This clutters the codebase.

Suggested change

// console.log('width', width);

// console.log('width > maxWidth', width > maxWidth);

// console.log('width < minWidth', width < minWidth);

// console.log(ratio)

// console.log(expectedRatio)

Copilot · 2025-12-18T06:32:18Z

@@ -0,0 +1,105 @@
+/**


There's a typo in the PR title: "scroping" should be "cropping".

Copilot · 2025-12-18T06:32:18Z

+					formData.append('rotation', data.additionalPicturesSettings[data.additionalPictures.indexOf(picture)].rotation.toString());
+					formData.append('crop', JSON.stringify(data.additionalPicturesSettings[data.additionalPictures.indexOf(picture)].crop));


Using indexOf inside a loop is inefficient and can return incorrect indices. If the same picture appears multiple times in the array, indexOf will always return the first occurrence. Store the index separately or use map with index parameter instead.

Copilot · 2025-12-18T06:32:20Z

+		try {
+			if (currentCroppingIndex === null || croppedAreaPixels === null) return;
+
+			const picture = currentCroppingIndex == 0 ? profilePicture : additionalPictures[currentCroppingIndex - 1];


Using loose equality (==) instead of strict equality (===). This should use === for type-safe comparison.

Copilot · 2025-12-18T06:32:20Z

    }

    update = async (id: number, user: UserProfile, location?: UserLocation) => {
+        console.log("Updating user ID:", id, "with data:", user, "and location:", location);


Debug console.log statement left in production code. This should be removed or wrapped in a development-only check.

Suggested change

console.log("Updating user ID:", id, "with data:", user, "and location:", location);

if (process.env.NODE_ENV !== 'production') {

console.debug("Updating user ID:", id, "with data:", user, "and location:", location);

}

Copilot · 2025-12-18T06:32:21Z

+            throw new BadRequestError('Failed to process image with given crop/rotation');
+        }
+
+        console.log('Saving new profile picture to', newFilePath);


Debug console.log statement left in production code. This should be removed or wrapped in a development-only check.

Suggested change

console.log('Saving new profile picture to', newFilePath);

if (process.env.NODE_ENV !== 'production') {

console.log('Saving new profile picture to', newFilePath);

}

Copilot · 2025-12-18T06:32:21Z

+const CROP_AREA_ASPECT = 9 / 16;



Unused variable CROP_AREA_ASPECT.

Suggested change

const CROP_AREA_ASPECT = 9 / 16;

Copilot · 2025-12-18T06:32:21Z

+		} catch (e) {
+			console.error(e)
+		}
+	}


Avoid automated semicolon insertion (91% of all statements in the enclosing function have an explicit semicolon).

Copilot

Pull request overview

Copilot reviewed 37 out of 40 changed files in this pull request and generated 11 comments.

Files not reviewed (1)

nextjs/matcha/pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (2)

nextjs/matcha/src/app/(logged)/me/page.tsx:170

These console.log statements on lines 148, 170, and should be removed before merging to production. Debug logging statements clutter the production console and may expose sensitive information.

  const { data: profile, isLoading, error, refetch } = useMyProfile();
  
  const [isUpdating, setIsUpdating] = useState(false);
  const [isUploading, setIsUploading] = useState(false);
  const [isDeleting, setIsDeleting] = useState(false);
  const [isSettingMain, setIsSettingMain] = useState(false);

  const [isEditing, setIsEditing] = useState(false);
  const [validationError, setValidationError] = useState<string | null>(null);
  const [formData, setFormData] = useState({
    firstName: "",
    lastName: "",
    email: "",
    bio: "",
    tags: [] as string[],
    gender: "",
    orientation: "",
    bornAt: "",
  });

  useEffect(() => {
    if (profile) {
      setFormData({

nextjs/matcha/src/hooks/useOnboarding.ts:5

Unused import Fira_Sans_Extra_Condensed.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-12-18T13:52:02Z

+  { value: "heterosexual", label: "Hétérosexuel" },
+  { value: "homosexual", label: "Homosexuel" },
+  { value: "bisexual", label: "Bisexuel" },
+]


Missing semicolon at the end of the array. This violates JavaScript/TypeScript coding standards and could cause issues with automatic semicolon insertion.

Copilot · 2025-12-18T13:52:03Z

+                    firstName: { type: 'string', minLength: 1, maxLength: 50, pattern: '[a-zA-Z-\' ]' },
+                    lastName: { type: 'string', minLength: 1, maxLength: 50, pattern: '[a-zA-Z-\' ]' },
                    email: { type: 'string', format: 'email' },
-                    bio: { type: 'string', minLength: 50, maxLength: 100 },
-                    tags: { type: 'array', items: { type: 'string' }, minItems: 1 },
+                    bio: { type: 'string', minLength: 50, maxLength: 500 },
+                    tags: { type: 'array', items: { type: 'string', minLength: 1, maxLength: 30, pattern: '[a-zA-Z_]' }, minItems: 3 },


The regex patterns in the schema definitions are missing delimiters. Patterns like '[a-zA-Z-' ]' and '[a-zA-Z_]' should be '^[a-zA-Z-' ]+$' and '^[a-zA-Z_]+$' respectively to properly validate the entire string. Without anchors, these patterns will match if any part of the string contains valid characters, allowing invalid input to pass validation.

Copilot · 2025-12-18T13:52:03Z

    }

    update = async (id: number, user: UserProfile, location?: UserLocation) => {
+        console.log("Updating user ID:", id, "with data:", user, "and location:", location);


Console.log statement should be removed before merging to production. This debug log on line 135 exposes potentially sensitive user data and should not be in production code.

Suggested change

console.log("Updating user ID:", id, "with data:", user, "and location:", location);

Copilot · 2025-12-18T13:52:03Z

 import { OnboardingData, OnboardingStep } from '@/types/onboarding';
 import { STEPS, MIN_INTERESTS } from '@/constants/onboarding';
 import { profileApi } from '@/lib/api/profile';
+import { Fira_Sans_Extra_Condensed } from 'next/font/google';


This import of 'Fira_Sans_Extra_Condensed' from 'next/font/google' appears to be unused. There's no reference to this font anywhere in the file. This should be removed to keep the codebase clean.

Copilot · 2025-12-18T13:52:04Z

+export default function getImageUrl(file: File | null): string | null {
+    return file ? URL.createObjectURL(file) : null;


There's a potential memory leak here. URL.createObjectURL creates a blob URL that needs to be explicitly revoked with URL.revokeObjectURL when no longer needed. Otherwise, the browser will keep the blob in memory until the page is closed. Consider implementing cleanup logic or using a useEffect hook with cleanup in components that use this function.

Copilot · 2025-12-18T13:52:04Z

+  if (query.error) {
+    query.error = new Error("Failed to fetch user profile");
+  }


The error assignment on line 80 is incorrect. You're trying to assign to a readonly property. The query.error property from useQuery is readonly and cannot be reassigned. This code will cause a runtime error. Instead, handle the error appropriately in the component or remove this line.

Copilot · 2025-12-18T13:52:04Z

+                    firstName: { type: 'string', minLength: 1, maxLength: 50, pattern: '[a-zA-Z-\' ]' },
+                    lastName: { type: 'string', minLength: 1, maxLength: 50, pattern: '[a-zA-Z-\' ]' },
+                    bio: { type: 'string', minLength: 50, maxLength: 500 },
+                    tags: { type: 'array', items: { type: 'string', minLength: 1, maxLength: 30, pattern: '[a-zA-Z_]' }, minItems: 3 },


The regex patterns in the schema definitions are missing delimiters. Patterns like '[a-zA-Z-' ]' should be '^[a-zA-Z-' ]+$' to properly validate the entire string. Without anchors (^ and $), the pattern will match if any part of the string contains valid characters, not the entire string.

Suggested change

firstName: { type: 'string', minLength: 1, maxLength: 50, pattern: '[a-zA-Z-\' ]' },

lastName: { type: 'string', minLength: 1, maxLength: 50, pattern: '[a-zA-Z-\' ]' },

bio: { type: 'string', minLength: 50, maxLength: 500 },

tags: { type: 'array', items: { type: 'string', minLength: 1, maxLength: 30, pattern: '[a-zA-Z_]' }, minItems: 3 },

firstName: { type: 'string', minLength: 1, maxLength: 50, pattern: '^[a-zA-Z-\' ]+$' },

lastName: { type: 'string', minLength: 1, maxLength: 50, pattern: '^[a-zA-Z-\' ]+$' },

bio: { type: 'string', minLength: 50, maxLength: 500 },

tags: { type: 'array', items: { type: 'string', minLength: 1, maxLength: 30, pattern: '^[a-zA-Z_]+' + '$' }, minItems: 3 },

Copilot · 2025-12-18T13:52:05Z

+    const gender = Math.random() > 0.5 ? "female" : "men";
+    const interestedInGenders = gender === "female" ? ["men"] : ["female"];


There's a logic error in the gender assignment. Line 370 assigns either "female" or "men" to the gender variable, mixing the old and new gender values. This should consistently use either the old values ("male"/"female") or new values ("men"/"women"). Based on other changes in the PR, it should be "women" instead of "female".

Copilot · 2025-12-18T13:52:05Z

  const router = useRouter();
  const queryClient = useQueryClient();
-  const { data: profile, isLoading, error } = useMyProfile();
+  const { data: profile, isLoading, error, refetch } = useMyProfile();


Unused variable refetch.

Suggested change

const { data: profile, isLoading, error, refetch } = useMyProfile();

const { data: profile, isLoading, error } = useMyProfile();

Copilot · 2025-12-18T13:52:05Z

+import IconButton from "@/components/common/IconButton";
+import ImageCropper from "@/components/common/ImageCropper";
+
+declare type Area = {
+    width: number;
+    height: number;


Unused import IconButton.

Suggested change

import IconButton from "@/components/common/IconButton";

import ImageCropper from "@/components/common/ImageCropper";

declare type Area = {

width: number;

height: number;

import ImageCropper from "@/components/common/ImageCropper";

declare type Area = {

width: number;

height: number;

height: number;

YoungMame added 8 commits November 27, 2025 17:12

add:(user edit profile page)

6cb7958

i react cropper component

4987c14

add:(simple image crop in onboarding)

aef87ab

add:(serveur image croping)

5f76118

add:(image settings to unboarding data)

bc982aa

fix:(image crop on unboarding)

caf5ea1

remove:(rotate svg)

9415c2e

add:(refacto in scropper in component)

0aaec99

YoungMame requested a review from ValentinMalassigne December 1, 2025 13:17

YoungMame self-assigned this Dec 1, 2025

Copilot AI review requested due to automatic review settings December 1, 2025 13:17

YoungMame added the enhancement New feature or request label Dec 1, 2025

YoungMame linked an issue Dec 1, 2025 that may be closed by this pull request

Image scroping in inscription form + Image upload error management #57

Closed

Copilot started reviewing on behalf of YoungMame December 1, 2025 13:17 View session

Copilot finished reviewing on behalf of YoungMame December 1, 2025 13:19

Copilot AI reviewed Dec 1, 2025

View reviewed changes

Copilot AI mentioned this pull request Dec 2, 2025

Fix image rotation to use 360 degrees instead of 180 #61

Merged

ValentinMalassigne and others added 3 commits December 18, 2025 06:50

Merge branch 'main' into 57-image-scroping-in-inscription-form-image-…

8bf7c8a

…upload-error-management

fix useHeader

4afdee0

Copilot AI review requested due to automatic review settings December 18, 2025 06:21

Copilot started reviewing on behalf of ValentinMalassigne December 18, 2025 06:21 View session

ValentinMalassigne approved these changes Dec 18, 2025

View reviewed changes

Copilot AI reviewed Dec 18, 2025

View reviewed changes

ValentinMalassigne and others added 2 commits December 18, 2025 07:34

remove trailing comma in package.json

b1ea979

add:(some client side data validation)

36cf974

Copilot AI review requested due to automatic review settings December 18, 2025 13:42

Copilot started reviewing on behalf of YoungMame December 18, 2025 13:42 View session

add:(clean comments)

7655afa

YoungMame merged commit 9ec8382 into main Dec 18, 2025
1 check failed

YoungMame deleted the 57-image-scroping-in-inscription-form-image-upload-error-management branch December 18, 2025 13:46

Copilot AI reviewed Dec 18, 2025

View reviewed changes

		const heightensAgo = today.setFullYear(today.getFullYear() - 18);

		if (heightensAgo - (me.birthdate as Date).getTime() < 0)

	function onChange(field: string, value: any) {
	console.log(`Field ${field} changed to`, value);
	}

	let rotation = Number((request.body as { rotation?: { value: string } }).rotation?.value) \|\| 0;
	if (rotation > 180) rotation = 180;
	if (rotation < -180) rotation = -180;

		formData.append('rotation', data.additionalPicturesSettings[data.additionalPictures.indexOf(picture)].rotation.toString());
		formData.append('crop', JSON.stringify(data.additionalPicturesSettings[data.additionalPictures.indexOf(picture)].crop));

-        console.log("Updating user ID:", id, "with data:", user, "and location:", location);
+        if (process.env.NODE_ENV !== 'production') {
+            console.debug("Updating user ID:", id, "with data:", user, "and location:", location);
+        }

		export default function getImageUrl(file: File \| null): string \| null {
		return file ? URL.createObjectURL(file) : null;

		const gender = Math.random() > 0.5 ? "female" : "men";
		const interestedInGenders = gender === "female" ? ["men"] : ["female"];

	const { data: profile, isLoading, error, refetch } = useMyProfile();
	const { data: profile, isLoading, error } = useMyProfile();

Conversation

YoungMame commented Dec 1, 2025

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Key Changes

Reviewed changes

Uh oh!

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment