Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing advertisment #3557 #3293

Conversation

udayempire
Copy link

@udayempire udayempire commented Feb 24, 2025

What kind of change does this PR introduce?

Code refactoring

Issue Number:

Fixes #3242

Snapshots/Videos:

https://www.loom.com/share/7988c722116945b892a7f7ddf8cd174b?sid=fed21822-8831-41ce-9637-707ba51a4a61

Summary

This PR enables the admin app to fetch multiple advertisement,storeimages and integrate with talawa admin app for advertisement section.

Does this PR introduce a breaking change?

No

Checklist

CodeRabbit AI Review

  • I have reviewed and addressed all critical issues flagged by CodeRabbit AI
  • I have implemented or provided justification for each non-critical suggestion
  • I have documented my reasoning in the PR comments where CodeRabbit AI suggestions were not implemented

Test Coverage

  • I have written tests for all new changes/features
  • I have verified that test coverage meets or exceeds 95%
  • I have run the test suite locally and all tests pass

Other information

Have you read the contributing guide?

Yes

Summary by CodeRabbit

  • New Features
    • Advertisement updates now support file attachments for enhanced flexibility.
    • A new query endpoint enables retrieval of advertisements by organization.
    • Expanded image upload capabilities to accept an additional JPEG format.

Copy link

coderabbitai bot commented Feb 24, 2025

Walkthrough

The pull request updates the GraphQL schema and related components to support file attachments and organization-based advertisement queries. Specifically, a new attachments field is added to the update advertisement mutation and a new advertisementsByOrg query is introduced with its respective input type. In addition, corresponding input validations, asynchronous processing for file uploads, and improved error handling were implemented. Minor documentation updates and an expansion of the image MIME type enum were also applied.

Changes

File(s) Change Summary
schema.graphql, src/graphql/inputs/MutationUpdateAdvertisementInput.ts, src/graphql/inputs/QueryAdvertisementsByOrgInput.ts, test/routes/graphql/gql.tada.d.ts Added new attachments field in the update advertisement mutation, a new advertisementsByOrg query, and QueryAdvertisementsByOrgInput input schema. Updated input validations and introspection types accordingly.
src/graphql/types/Mutation/createAdvertisement.ts, src/graphql/types/Mutation/updateAdvertisement.ts, src/graphql/types/Query/advertisement.ts Enhanced resolver logic with asynchronous validation, file upload handling (including MIME type checks), improved logging, and added authentication/authorization checks.
src/drizzle/enums/imageMimeType.ts, src/drizzle/tables/advertisements.ts, src/graphql/inputs/MutationCreateAdvertisementInput.ts Extended the image MIME type enum with "image/jpg", updated file comments for Drizzle ORM table definitions, and added documentation comments to clarify the purpose of the MutationCreateAdvertisementInput file.

Sequence Diagram(s)

sequenceDiagram
    participant C as Client
    participant G as GraphQL Resolver (advertisementsByOrg)
    participant A as Authentication Module
    participant O as Organization Service
    participant DB as Database

    C->>G: Send advertisementsByOrg query with organizationId
    G->>A: Verify client authentication
    A-->>G: Authentication successful
    G->>G: Parse input using QueryAdvertisementsByOrgInput schema
    G->>O: Fetch organization by organizationId
    O-->>G: Return organization details (or error if not found)
    G->>DB: Query advertisements linked to organization
    DB-->>G: Return advertisements list
    G->>C: Respond with advertisements and attachments
Loading
sequenceDiagram
    participant C as Client
    participant G as GraphQL Resolver (updateAdvertisement)
    participant A as Async Validator
    participant DB as Database

    C->>G: Send update advertisement mutation with attachments
    G->>A: Validate input asynchronously (using safeParseAsync)
    A-->>G: Return validated input including attachments
    G->>DB: Update advertisement record and insert attachments if provided
    DB-->>G: Return updated advertisement record
    G->>C: Respond with updated advertisement
Loading

Possibly related PRs

Suggested labels

GSoC Priority, ignore-sensitive-files-pr

Suggested reviewers

  • palisadoes
✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Congratulations on making your first PR! 🎊 If you haven't already, check out our Contributing Guidelines and PR Reporting Guidelines to ensure that you are following our guidelines for contributing and creating PR.

Copy link

codecov bot commented Feb 24, 2025

Codecov Report

Attention: Patch coverage is 19.46903% with 182 lines in your changes missing coverage. Please review.

Project coverage is 48.18%. Comparing base (2438e61) to head (020a667).
Report is 7 commits behind head on develop-postgres.

Files with missing lines Patch % Lines
src/graphql/types/Query/advertisement.ts 22.42% 83 Missing ⚠️
src/graphql/types/Mutation/updateAdvertisement.ts 7.04% 66 Missing ⚠️
...rc/graphql/inputs/QueryAdvertisementsByOrgInput.ts 0.00% 21 Missing ⚠️
...graphql/inputs/MutationUpdateAdvertisementInput.ts 56.00% 11 Missing ⚠️
src/graphql/types/Mutation/createAdvertisement.ts 0.00% 1 Missing ⚠️
Additional details and impacted files
@@                 Coverage Diff                  @@
##           develop-postgres    #3293      +/-   ##
====================================================
- Coverage             48.36%   48.18%   -0.19%     
====================================================
  Files                   458      459       +1     
  Lines                 34516    34727     +211     
  Branches                966      967       +1     
====================================================
+ Hits                  16695    16733      +38     
- Misses                17821    17994     +173     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 13

🔭 Outside diff range comments (1)
schema.graphql (1)

2841-2918: 🧹 Nitpick (assertive)

Consider adding pagination support.

The advertisementsByOrg query returns an array of advertisements but lacks pagination support. For better scalability and performance, consider implementing pagination using the existing connection pattern used throughout the schema.

-  advertisementsByOrg(input: QueryAdvertisementsByOrgInput!): [Advertisement!]
+  advertisementsByOrg(
+    input: QueryAdvertisementsByOrgInput!
+    after: String
+    before: String
+    first: Int
+    last: Int
+  ): AdvertisementsByOrgConnection!

+type AdvertisementsByOrgConnection {
+  edges: [AdvertisementsByOrgConnectionEdge]
+  pageInfo: PageInfo!
+}

+type AdvertisementsByOrgConnectionEdge {
+  cursor: String!
+  node: Advertisement
+}
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2438e61 and 020a667.

📒 Files selected for processing (10)
  • schema.graphql (3 hunks)
  • src/drizzle/enums/imageMimeType.ts (1 hunks)
  • src/drizzle/tables/advertisements.ts (1 hunks)
  • src/graphql/inputs/MutationCreateAdvertisementInput.ts (1 hunks)
  • src/graphql/inputs/MutationUpdateAdvertisementInput.ts (2 hunks)
  • src/graphql/inputs/QueryAdvertisementsByOrgInput.ts (1 hunks)
  • src/graphql/types/Mutation/createAdvertisement.ts (3 hunks)
  • src/graphql/types/Mutation/updateAdvertisement.ts (4 hunks)
  • src/graphql/types/Query/advertisement.ts (1 hunks)
  • test/routes/graphql/gql.tada.d.ts (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Run tests for talawa api
  • GitHub Check: Analyse Code With CodeQL (typescript)
🔇 Additional comments (12)
src/graphql/inputs/MutationCreateAdvertisementInput.ts (1)

7-8: 🧹 Nitpick (assertive)

Fix grammatical error in the comment.

The comment has a minor grammatical error. "This file" should be used instead of "These file".

-//This file defines the input for the createAdvertisement mutation. It uses a Zod schema to validate and transform incoming data and then exposes it as a GraphQL input type.
+// This file defines the input for the createAdvertisement mutation. It uses a Zod schema to validate and transform incoming data and then exposes it as a GraphQL input type.

Likely an incorrect or invalid review comment.

src/graphql/inputs/QueryAdvertisementsByOrgInput.ts (1)

5-24: LGTM!

The implementation follows best practices:

  • Uses Zod schema for input validation
  • Includes UUID format validation with a clear error message
  • Properly documents the input type and fields
src/graphql/types/Mutation/createAdvertisement.ts (1)

67-67: LGTM!

The comment clearly describes the purpose of the mutation field.

schema.graphql (1)

2032-2033: LGTM!

The attachments field is properly defined with a clear description and appropriate type.

src/graphql/inputs/MutationUpdateAdvertisementInput.ts (1)

10-10: LGTM!

Using partial() is appropriate for an update mutation as it makes all fields optional.

test/routes/graphql/gql.tada.d.ts (2)

97-97: Good addition for advertisement updates.
The newly introduced attachments field in MutationUpdateAdvertisementInput is consistent with the rest of the schema and properly aligns with the updates for handling file uploads.


152-152: Query field looks properly introduced.
Including advertisementsByOrg under Query is coherent with the schema changes.

src/graphql/types/Query/advertisement.ts (1)

137-248: Robust membership checks.
The advertisementsByOrg resolver is well-structured, with appropriate authentication and authorization checks. The safe parsing logic ensures input validity, and error handling is consistent with the rest of the code.

src/graphql/types/Mutation/updateAdvertisement.ts (4)

2-2: Check compatibility of FileUpload type.
Ensure the graphql-upload-minimal version aligns with the rest of the application and is regularly maintained.


3-3: Use of ULID is appropriate.
ULIDs provide a good level of uniqueness for distributed systems.


5-5: Import usage confirmed.
Referencing the advertisementAttachmentMimeTypeEnum is consistent with your upload validation logic.


78-78: Asynchronous safe parsing is properly applied.
This approach correctly handles the async transformations, though confirm that partial validation failures are acceptable for your use case.

Comment on lines 17 to 19
/**
* Drizzle orm postgres table definition for advertisements.
* These file define how data is stored in your PostgreSQL database using Drizzle ORM.
*/
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Fix grammatical error in the comment.

The comment has a similar grammatical error. "This file" should be used instead of "These file".

 /**
- * These file define how data is stored in your PostgreSQL database using Drizzle ORM.
+ * This file defines how data is stored in your PostgreSQL database using Drizzle ORM.
 */
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
/**
* Drizzle orm postgres table definition for advertisements.
* These file define how data is stored in your PostgreSQL database using Drizzle ORM.
*/
/**
* This file defines how data is stored in your PostgreSQL database using Drizzle ORM.
*/

Comment on lines 6 to 12
export const imageMimeTypeEnum = z.enum([
"image/avif",
"image/jpeg",
"image/jpg",
"image/png",
"image/webp",
]);
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Consider removing redundant MIME type.

"image/jpg" is redundant as "image/jpeg" is already included and is the official MIME type according to IANA standards. Having both might lead to inconsistencies in file handling.

export const imageMimeTypeEnum = z.enum([
	"image/avif",
	"image/jpeg",
-	"image/jpg",
	"image/png",
	"image/webp",
]);
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
export const imageMimeTypeEnum = z.enum([
"image/avif",
"image/jpeg",
"image/jpg",
"image/png",
"image/webp",
]);
export const imageMimeTypeEnum = z.enum([
"image/avif",
"image/jpeg",
"image/png",
"image/webp",
]);

import { z } from "zod";
import { builder } from "~/src/graphql/builder";

//query to fetch multiple organuisation by organisationID
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Fix typo in the comment.

The comment has a typo: "organuisation" should be "organization".

-//query to fetch multiple organuisation by organisationID
+// Query to fetch multiple organizations by organizationID
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
//query to fetch multiple organuisation by organisationID
// Query to fetch multiple organizations by organizationID

@@ -12,14 +12,16 @@
import { Advertisement } from "~/src/graphql/types/Advertisement/Advertisement";
import { TalawaGraphQLError } from "~/src/utilities/TalawaGraphQLError";

//This file contains the logic for the createAdvertisement mutation.It Handles input validation, database insertion, file uploads to MinIO, and metadata storage for the createAdvertisement mutation.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Improve comment formatting.

The comment provides good context but could be formatted better for readability.

-//This file contains the logic for the createAdvertisement mutation.It Handles input validation, database insertion, file uploads to MinIO, and metadata storage for the createAdvertisement mutation.
+// This file contains the logic for the createAdvertisement mutation. It handles:
+// - Input validation
+// - Database insertion
+// - File uploads to MinIO
+// - Metadata storage
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
//This file contains the logic for the createAdvertisement mutation.It Handles input validation, database insertion, file uploads to MinIO, and metadata storage for the createAdvertisement mutation.
// This file contains the logic for the createAdvertisement mutation. It handles:
// - Input validation
// - Database insertion
// - File uploads to MinIO
// - Metadata storage

@@ -161,7 +164,7 @@
},
});
}

//Prevents unauthorized users from creating advertisements
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Remove redundant comment.

The comment is redundant as the code block below it is self-documenting through the clear variable name currentUserOrganizationMembership and the role check.

-//Prevents unauthorized users from creating advertisements
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
//Prevents unauthorized users from creating advertisements

'QueryAdvertisementInput': { kind: 'INPUT_OBJECT'; name: 'QueryAdvertisementInput'; isOneOf: false; inputFields: [{ name: 'id'; type: { kind: 'NON_NULL'; name: never; ofType: { kind: 'SCALAR'; name: 'String'; ofType: null; }; }; defaultValue: null }]; };
'QueryAdvertisementsByOrgInput': { kind: 'INPUT_OBJECT'; name: 'QueryAdvertisementsByOrgInput'; isOneOf: false; inputFields: [{ name: 'organizationId'; type: { kind: 'NON_NULL'; name: never; ofType: { kind: 'SCALAR'; name: 'String'; ofType: null; }; }; defaultValue: null }]; };
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Consider extra validation for organizationId.
While the schema is correct as-is, adding validation (e.g., non-empty checks) might help avoid edge cases with invalid IDs.

@@ -127,3 +127,122 @@
type: Advertisement,
}),
);
//To Fetch All Advertisment for a particular organistation by user.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Minor comment style suggestion.
Consider matching the spelling of "organization" consistently throughout the codebase.

Comment on lines +131 to +135
const queryAdvertisementsByOrgInputSchema = z.object({
input: z.object({
organizationId: z.string(),
}),
});
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Enhance input schema checks.
The current schema only requires organizationId to be a string. Consider verifying it’s not empty to handle potential misuse.

Comment on lines +17 to +52
input: mutationUpdateAdvertisementInputSchema.transform(async (arg, ctx) => {
let attachments:
| (FileUpload & {
mimetype: z.infer<typeof advertisementAttachmentMimeTypeEnum>;
})[]
| undefined;
console.log("Raw attachments:", arg.attachments);
if (arg.attachments !== undefined) {
const rawAttachments = await Promise.all(arg.attachments);
const { data, error, success } = advertisementAttachmentMimeTypeEnum
.array()
.safeParse(rawAttachments.map((attachment) => attachment.mimetype));

if (!success) {
for (const issue of error.issues) {
if (typeof issue.path[0] === "number") {
ctx.addIssue({
code: "custom",
path: ["attachments", issue.path[0]],
message: `Mime type "${rawAttachments[issue.path[0]]?.mimetype}" is not allowed.`,
});
}
}
} else {
attachments = rawAttachments.map((attachment, index) =>
Object.assign(attachment, {
mimetype: data[index],
}),
);
}
}
return {
...arg,
attachments,
};
}),
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Console logging & attachment size validation.
While console logging can be helpful during development, consider replacing it with a more formal logging mechanism. Additionally, imposing size/quantity limits on attachments might prevent excessive resource usage.

Comment on lines +261 to +293
if (parsedArgs.input.attachments !== undefined) {
const attachments = parsedArgs.input.attachments;
const updatedAdvertisementAttachments = await ctx.drizzleClient
.insert(advertisementAttachmentsTable)
.values(
attachments.map((attachment) => ({
advertisementId: updatedAdvertisement.id,
creatorId: currentUserId,
mimeType: attachment.mimetype,
name: ulid(),
})),
)
.onConflictDoNothing()
.returning();

if (Array.isArray(updatedAdvertisementAttachments)) {
await Promise.all(
updatedAdvertisementAttachments.map((attachment, index) => {
if (attachments[index] !== undefined) {
return ctx.minio.client.putObject(
ctx.minio.bucketName,
attachment.name,
attachments[index].createReadStream(),
undefined,
{
"content-type": attachments[index].mimetype,
},
);
}
}),
);
}
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Improve error handling & concurrency control.
Inserting attachments and uploading to MinIO is solid. Consider handling partial failures in a transaction or limiting concurrency so that one failing upload doesn’t leave the database in an inconsistent state.

@udayempire
Copy link
Author

Okay I will try to cover this rabbit ai requested changes and add commits thanks

@palisadoes
Copy link
Contributor

  1. Please make coderabbit.ai approves your work.
  2. Make sure all tests pass and are valid.
  3. Ensure the test code coverage for your patch reaches as close to 100% as possible.

image

@palisadoes
Copy link
Contributor

@palisadoes palisadoes closed this Feb 27, 2025
@coderabbitai coderabbitai bot mentioned this pull request Feb 27, 2025
@udayempire
Copy link
Author

@palisadoes Sir but in this pr I also had worked on attachments to be fetched and uploaded succesfully. I know we dont want to do it from backend but still untill we solve the issue of uploading through frontend we may let it work? let me know your opinions please.

@coderabbitai coderabbitai bot mentioned this pull request Mar 1, 2025
@palisadoes
Copy link
Contributor

Submit an updated PR based on the approach from @xoldd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants