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

Plugin and advertisement screen revamp #2006

Conversation

duplixx
Copy link
Contributor

@duplixx duplixx commented May 24, 2024

What kind of change does this PR introduce?

Redesign

Issue Number:

Fixes #1918

Did you add tests for your changes?

No

Snapshots/Videos:
image
image

If relevant, did you update the documentation?

Summary

Does this PR introduce a breaking change?

Other information

Have you read the contributing guide?

Summary by CodeRabbit

  • New Features

    • Renamed "Add On Store" to "Plugin Store" for better clarity.
    • Updated button text from "Create new advertisement" to "Create" for consistency.
  • Bug Fixes

    • Improved error handling and optional chaining in various components to enhance stability.
  • Style

    • Updated styles for cards, inputs, and grid layouts for a more polished look.
    • Introduced media queries for better responsive design.
  • Refactor

    • Refactored types and interfaces for improved code maintainability and readability.
    • Enhanced the generateLinks function to include more detailed plugin information.

Copy link

coderabbitai bot commented May 24, 2024

Walkthrough

The changes involve a comprehensive redesign of the advertisement and plugin screens in the admin portal. Key updates include renaming labels, enhancing CSS for better styling, improving type safety in TypeScript, and refining component logic. These adjustments aim to align with the new design specifications, ensuring a more consistent and visually appealing user interface.

Changes

Files/Paths Change Summary
public/locales/en.json Renamed "Add On Store" to "Plugin Store"; updated button text from "Create new advertisement" to "Create".
src/components/ActionItems/ActionItemsModal.tsx Updated optional chaining for props object properties.
src/components/AddOn/core/AddOnEntry/AddOnEntry.module.css Added green border to .card class.
src/components/AddOn/core/AddOnEntry/AddOnEntry.tsx Changed modified property to boolean; updated getInstalledPlugins return type to void.
src/components/AddOn/core/AddOnStore/AddOnStore.module.css Renamed .actioninput to .input; added new styles and media queries.
src/components/AddOn/core/AddOnStore/AddOnStore.tsx Added imports, modified state and hook types, refactored functions, and adjusted JSX structure.
src/components/AddOn/support/services/Plugin.helper.test.ts, src/components/AddOn/support/services/Plugin.helper.ts Enhanced generateLinks function; introduced InterfacePluginHelper and updated method signatures.
src/components/Advertisements/Advertisements.module.css Updated styles for various classes.
src/components/Advertisements/Advertisements.tsx Added imports, modified components and styles, updated logic for displaying plugin entries.
src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.module.css Adjusted .admedia and .card class styles.
src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.tsx Refactored types, updated function signatures, improved error handling, and adjusted styling.
src/components/Advertisements/core/AdvertisementRegister/AdvertisementRegister.module.css Adjusted height and margin properties for specific classes.
src/components/Advertisements/core/AdvertisementRegister/AdvertisementRegister.tsx Updated setAfter property in InterfaceAddOnRegisterProps, improved error handling.
src/components/EventCalendar/EventCalendar.module.css Added a blank line between two CSS rules.

Assessment against linked issues

Objective (Issue #1918) Addressed Explanation
Redesign advertisement and plugin screens
Ensure consistency in button text and labels
Improve type safety and error handling in TypeScript
Enhance CSS for better styling and responsiveness

In the code's garden, changes bloom,
With green borders and styles that loom.
Plugins now in a store so bright,
Advertisements shine with all their might.
The rabbit hops, with joy and glee,
For code and art in harmony. 🌸🐇

Tip

New Features and Improvements

Review Settings

Introduced new personality profiles for code reviews. Users can now select between "Chill" and "Assertive" review tones to tailor feedback styles according to their preferences. The "Assertive" profile posts more comments and nitpicks the code more aggressively, while the "Chill" profile is more relaxed and posts fewer comments.

AST-based Instructions

CodeRabbit offers customizing reviews based on the Abstract Syntax Tree (AST) pattern matching. Read more about AST-based instructions in the documentation.

Community-driven AST-based Rules

We are kicking off a community-driven initiative to create and share AST-based rules. Users can now contribute their AST-based rules to detect security vulnerabilities, code smells, and anti-patterns. Please see the ast-grep-essentials repository for more information.

New Static Analysis Tools

We are continually expanding our support for static analysis tools. We have added support for biome, hadolint, and ast-grep. Update the settings in your .coderabbit.yaml file or head over to the settings page to enable or disable the tools you want to use.

Tone Settings

Users can now customize CodeRabbit to review code in the style of their favorite characters or personalities. Here are some of our favorite examples:

  • Mr. T: "You must talk like Mr. T in all your code reviews. I pity the fool who doesn't!"
  • Pirate: "Arr, matey! Ye must talk like a pirate in all yer code reviews. Yarrr!"
  • Snarky: "You must be snarky in all your code reviews. Snark, snark, snark!"

Revamped Settings Page

We have redesigned the settings page for a more intuitive layout, enabling users to find and adjust settings quickly. This change was long overdue; it not only improves the user experience but also allows our development team to add more settings in the future with ease. Going forward, the changes to .coderabbit.yaml will be reflected in the settings page, and vice versa.

Miscellaneous

  • Turn off free summarization: You can switch off free summarization of PRs opened by users not on a paid plan using the enable_free_tier setting.
  • Knowledge-base scope: You can now set the scope of the knowledge base to either the repository (local) or the organization (global) level using the knowledge_base setting. In addition, you can specify Jira project keys and Linear team keys to limit the knowledge base scope for those integrations.
  • High-level summary placement: You can now customize the location of the high-level summary in the PR description using the high_level_summary_placeholder setting (default @coderabbitai summary).
  • Revamped request changes workflow: You can now configure CodeRabbit to auto-approve or request changes on PRs based on the review feedback using the request_changes_workflow setting.

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

  1. The overall code coverage drops below the target threshold of the repository
  2. Any file in the pull request has code coverage levels below the repository threshold
  3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

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

@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: 8

Outside diff range and nitpick comments (12)
src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.tsx (3)

Line range hint 77-81: Specify the type attribute for the button to ensure correct behavior in forms.

+ type="button"

Line range hint 99-99: Add keyboard accessibility to the delete button by handling key events.

+ onKeyUp={(event) => { if (event.key === 'Enter') toggleShowDeleteModal(); }}

Line range hint 147-147: Self-close JSX elements that don't have children.

- <Card.Img className={styles.admedia} variant="top" src={mediaUrl} data-testid="media"></Card.Img>
+ <Card.Img className={styles.admedia} variant="top" src={mediaUrl} data-testid="media" />

Also applies to: 158-158

src/components/AddOn/core/AddOnStore/AddOnStore.tsx (1)

Line range hint 75-75: Self-close JSX elements that don't have children.

- <div className={styles.loader}></div>
+ <div className={styles.loader} />
src/components/Advertisements/Advertisements.tsx (3)

Line range hint 53-53: Use optional chaining to safely access nested properties.

- orgAdvertisementListData && orgAdvertisementListData.organizations
+ orgAdvertisementListData?.organizations

Also applies to: 67-67


Line range hint 126-128: Self-close JSX elements that don't have children.

- <div className={styles.itemCard}></div>
+ <div className={styles.itemCard} />

Also applies to: 130-130, 205-207, 209-209


Line range hint 123-123: Avoid using the index of an array as a key in React lists.

- key={index}
+ key={`ad-${index}`}

Also applies to: 176-176, 202-202, 255-255

src/components/Advertisements/core/AdvertisementRegister/AdvertisementRegister.tsx (5)

Line range hint 217-217: Self-close JSX elements that don't have children.

- <video></video>
+ <video />

Also applies to: 312-312


Line range hint 221-221: Add keyboard accessibility to interactive elements by handling key events.

+ onKeyUp={(event) => { if (event.key === 'Enter') handleShow(); }}

Line range hint 267-267: Use optional chaining to safely access nested properties.

- if (error instanceof Error) {
+ if (error?.message) {

Line range hint 292-293: Provide alt text for images to improve accessibility.

- <img src={formState.advertisementMedia} />
+ <img src={formState.advertisementMedia} alt="Advertisement Media" />

Line range hint 295-311: Specify the type attribute for buttons to ensure correct behavior in forms.

+ type="button"
Review Details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits Files that changed from the base of the PR and between 7993f66 and 6173faf.
Files selected for processing (15)
  • public/locales/en.json (2 hunks)
  • src/components/ActionItems/ActionItemsModal.tsx (2 hunks)
  • src/components/AddOn/core/AddOnEntry/AddOnEntry.module.css (1 hunks)
  • src/components/AddOn/core/AddOnEntry/AddOnEntry.tsx (5 hunks)
  • src/components/AddOn/core/AddOnStore/AddOnStore.module.css (2 hunks)
  • src/components/AddOn/core/AddOnStore/AddOnStore.tsx (6 hunks)
  • src/components/AddOn/support/services/Plugin.helper.test.ts (1 hunks)
  • src/components/AddOn/support/services/Plugin.helper.ts (1 hunks)
  • src/components/Advertisements/Advertisements.module.css (2 hunks)
  • src/components/Advertisements/Advertisements.tsx (7 hunks)
  • src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.module.css (1 hunks)
  • src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.tsx (6 hunks)
  • src/components/Advertisements/core/AdvertisementRegister/AdvertisementRegister.module.css (1 hunks)
  • src/components/Advertisements/core/AdvertisementRegister/AdvertisementRegister.tsx (2 hunks)
  • src/components/EventCalendar/EventCalendar.module.css (1 hunks)
Files not reviewed due to errors (3)
  • src/components/AddOn/core/AddOnStore/AddOnStore.module.css (no review received)
  • src/components/AddOn/support/services/Plugin.helper.test.ts (no review received)
  • src/components/AddOn/core/AddOnEntry/AddOnEntry.tsx (no review received)
Files skipped from review due to trivial changes (5)
  • public/locales/en.json
  • src/components/ActionItems/ActionItemsModal.tsx
  • src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.module.css
  • src/components/Advertisements/core/AdvertisementRegister/AdvertisementRegister.module.css
  • src/components/EventCalendar/EventCalendar.module.css
Additional Context Used
Biome (42)
src/components/AddOn/core/AddOnEntry/AddOnEntry.tsx (1)

102-104: JSX elements without children should be marked as self-closing. In JSX, it is valid for any element to be self-closing.

src/components/AddOn/core/AddOnStore/AddOnStore.tsx (12)

75-75: JSX elements without children should be marked as self-closing. In JSX, it is valid for any element to be self-closing.


108-108: Do not use template literals if interpolation and special-character handling are not needed.


144-144: Use === instead of ==.
== is only allowed when comparing against null


146-152: This else clause can be omitted because previous branches break early.


159-159: Use === instead of ==.
== is only allowed when comparing against null


161-167: This else clause can be omitted because previous branches break early.


202-208: This else clause can be omitted because previous branches break early.


218-218: Use === instead of ==.
== is only allowed when comparing against null


220-226: This else clause can be omitted because previous branches break early.


1-1: The default import is only used as a type.


174-174: Avoid using the index of an array as key property in an element.


233-233: Avoid using the index of an array as key property in an element.

src/components/AddOn/support/services/Plugin.helper.ts (1)

22-22: Do not use template literals if interpolation and special-character handling are not needed.

src/components/Advertisements/Advertisements.tsx (16)

38-38: Unexpected any. Specify a different type.


53-53: Change to an optional chain.


67-67: Change to an optional chain.


99-99: Do not use template literals if interpolation and special-character handling are not needed.


126-128: JSX elements without children should be marked as self-closing. In JSX, it is valid for any element to be self-closing.


130-130: JSX elements without children should be marked as self-closing. In JSX, it is valid for any element to be self-closing.


130-130: Provide screen reader accessible content when using heading elements.


205-207: JSX elements without children should be marked as self-closing. In JSX, it is valid for any element to be self-closing.


209-209: JSX elements without children should be marked as self-closing. In JSX, it is valid for any element to be self-closing.


209-209: Provide screen reader accessible content when using heading elements.


1-1: The default import is only used as a type.


52-52: This hook does not specify all of its dependencies: advertisements


123-123: Avoid using the index of an array as key property in an element.


176-176: Avoid using the index of an array as key property in an element.


202-202: Avoid using the index of an array as key property in an element.


255-255: Avoid using the index of an array as key property in an element.

src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.tsx (5)

99-99: Enforce to have the onClick mouse event with the onKeyUp, the onKeyDown, or the onKeyPress keyboard event.


147-147: JSX elements without children should be marked as self-closing. In JSX, it is valid for any element to be self-closing.


158-158: JSX elements without children should be marked as self-closing. In JSX, it is valid for any element to be self-closing.


74-74: Avoid using the index of an array as key property in an element.


77-81: Provide an explicit type prop for the button element.

src/components/Advertisements/core/AdvertisementRegister/AdvertisementRegister.tsx (7)

217-217: JSX elements without children should be marked as self-closing. In JSX, it is valid for any element to be self-closing.


221-221: Enforce to have the onClick mouse event with the onKeyUp, the onKeyDown, or the onKeyPress keyboard event.


267-267: Change to an optional chain.


292-293: Provide a text alternative through the alt, aria-label or aria-labelledby attribute


312-312: JSX elements without children should be marked as self-closing. In JSX, it is valid for any element to be self-closing.


1-1: The default import is only used as a type.


295-311: Provide an explicit type prop for the button element.

Additional comments not posted (9)
src/components/AddOn/core/AddOnEntry/AddOnEntry.module.css (2)

10-11: Updated background and text color for .entryaction class enhances visual consistency and appeal.


14-14: Green border addition to .card class aligns with the redesign objectives to make UI elements more visually appealing.

src/components/Advertisements/Advertisements.module.css (3)

4-10: Updated .listBox to use grid layout enhances alignment and spacing, improving the visual structure of the component.


21-25: Updated .input class with specific width and position settings enhances control over the layout and appearance.


26-30: Updated .justifysp to use grid layout enhances alignment and spacing, improving the visual structure of the component.

src/components/AddOn/support/services/Plugin.helper.ts (3)

1-12: Introduction of InterfacePluginHelper enhances type safety and clarity in handling plugin data.


26-31: Refinement of generateLinks to use InterfacePluginHelper enhances data handling and consistency.


15-18: Ensure type consistency by updating the return type of fetchStore to Promise<InterfacePluginHelper[]>.

- const result = await fetch(`http://localhost:${port}/store`);
+ const result = await fetch('http://localhost:4321/store');

Avoid using template literals when not necessary for interpolation.

Likely invalid or redundant comment.

src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.tsx (1)

21-21: Ensure the setAfter function is properly documented and tested, especially since it's part of the component's interface.

Comment on lines +60 to +64
} catch (error: unknown) {
if (error instanceof Error) {
toast.error(error.message);
setButtonLoading(false);
}
Copy link

Choose a reason for hiding this comment

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

Improve error handling by logging the error details for better debugging.

+ console.error("Error deleting advertisement:", error);

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.

Suggested change
} catch (error: unknown) {
if (error instanceof Error) {
toast.error(error.message);
setButtonLoading(false);
}
} catch (error: unknown) {
if (error instanceof Error) {
console.error("Error deleting advertisement:", error);
toast.error(error.message);
setButtonLoading(false);
}

@@ -77,7 +72,7 @@
<Row data-testid="AdEntry" xs={1} md={2} className="g-4">
{Array.from({ length: 1 }).map((_, idx) => (
<Col key={idx}>
<Card>
<Card className={styles.card}>
Copy link

Choose a reason for hiding this comment

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

Avoid using array index as a key in React lists due to potential issues with item reordering and performance.

- <Col key={idx}>
+ <Col key={`col-${idx}`}>

Committable suggestion was skipped due low confidence.

@@ -87,86 +104,58 @@ function addOnStore(): JSX.Element {
required
onChange={(e): void => setSearchText(e.target.value)}
/>
</Action>
<Button
className={`position-absolute z-10 bottom-0 end-0 d-flex justify-content-center align-items-center `}
Copy link

Choose a reason for hiding this comment

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

Remove unnecessary template literals for better performance and readability.

- className={`position-absolute z-10 bottom-0 end-0 d-flex justify-content-center align-items-center `}
+ className="position-absolute z-10 bottom-0 end-0 d-flex justify-content-center align-items-center"

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.

Suggested change
className={`position-absolute z-10 bottom-0 end-0 d-flex justify-content-center align-items-center `}
className="position-absolute z-10 bottom-0 end-0 d-flex justify-content-center align-items-center"

).length === 0 ? (
<div className={styles.justifysp}>
{data?.getPlugins.filter((val: InterfacePluginHelper) => {
if (searchText == '') {
Copy link

Choose a reason for hiding this comment

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

Use strict equality checks (===) instead of loose equality (==) to avoid unexpected type coercion.

- if (searchText == '') {
+ if (searchText === '') {

Also applies to: 159-159, 218-218


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.

Suggested change
if (searchText == '') {
if (searchText === '') {

plug: InterfacePluginHelper,
i: React.Key | null | undefined,
): JSX.Element => (
<div className={styles.cardGridItem} key={i}>
Copy link

Choose a reason for hiding this comment

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

Avoid using the index of an array as a key in React lists.

- key={i}
+ key={`plugin-${plug._id}`}

Also applies to: 233-233


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.

Suggested change
<div className={styles.cardGridItem} key={i}>
<div className={styles.cardGridItem} key={`plugin-${plug._id}`}>

Comment on lines +146 to +152
} else if (
val.pluginName
?.toLowerCase()
.includes(searchText.toLowerCase())
) {
return val;
}
Copy link

Choose a reason for hiding this comment

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

Remove unnecessary else clauses after return statements to simplify the logic.

- } else if (
+ if (

Also applies to: 161-167, 202-208


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.

Suggested change
} else if (
val.pluginName
?.toLowerCase()
.includes(searchText.toLowerCase())
) {
return val;
}
}
if (
val.pluginName
?.toLowerCase()
.includes(searchText.toLowerCase())
) {
return val;
}

@@ -32,6 +34,7 @@ export default function advertisements(): JSX.Element {
data?: {
organizations: InterfaceQueryOrganizationAdvertisementListItem[];
};
// eslint-disable-next-line
refetch: any;
Copy link

Choose a reason for hiding this comment

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

Specify a more appropriate type instead of any for the refetch function to ensure type safety.

- refetch: any;
+ refetch: () => Promise<void>;

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.

Suggested change
refetch: any;
refetch: () => Promise<void>;

// onChange={(e): void => setSearchText("search")}
/>
<Button
className={`position-absolute z-10 bottom-0 end-0 d-flex justify-content-center align-items-center `}
Copy link

Choose a reason for hiding this comment

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

Remove unnecessary template literals for better performance and readability.

- className={`position-absolute z-10 bottom-0 end-0 d-flex justify-content-center align-items-center `}
+ className="position-absolute z-10 bottom-0 end-0 d-flex justify-content-center align-items-center"

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.

Suggested change
className={`position-absolute z-10 bottom-0 end-0 d-flex justify-content-center align-items-center `}
className="position-absolute z-10 bottom-0 end-0 d-flex justify-content-center align-items-center"

@palisadoes
Copy link
Contributor

Please make the suggested code rabbit updates to the code

@palisadoes
Copy link
Contributor

Please fix the conflicting files and address the coderabbit suggestions

@duplixx
Copy link
Contributor Author

duplixx commented Jun 5, 2024

sorry for late response i'll make the suggested changes

Copy link

This pull request did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please verify it has no conflicts with the develop branch and rebase if needed. Mention it now if you need help or give permission to other people to finish your work.

@github-actions github-actions bot added the no-pr-activity No pull request activity label Jun 16, 2024
@palisadoes
Copy link
Contributor

Please fix the conflicting files.

@github-actions github-actions bot removed the no-pr-activity No pull request activity label Jun 18, 2024
Copy link

This pull request did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please verify it has no conflicts with the develop branch and rebase if needed. Mention it now if you need help or give permission to other people to finish your work.

@github-actions github-actions bot added the no-pr-activity No pull request activity label Jun 29, 2024
@palisadoes
Copy link
Contributor

Closing. Inactivity and many conflicting files

@palisadoes palisadoes closed this Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-pr-activity No pull request activity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants