Skip to content

refactor: reduce code duplication #688

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

anyulled
Copy link
Member

@anyulled anyulled commented Apr 1, 2025

No description provided.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Hello @anyulled, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

This pull request focuses on reducing code duplication by creating a common Speakers component and associated styling. It moves the Speakers2023 and Speakers2024 components, which were previously located in year-specific directories, into a new components/YearSpecific/Speakers directory. The App.tsx file is updated to import these components from their new location.

Highlights

  • Code Duplication Reduction: The primary goal is to reduce code duplication by creating a reusable Speakers component.
  • Component Relocation: Speakers2023 and Speakers2024 components are moved to components/YearSpecific/Speakers.
  • Import Path Updates: The import statements in App.tsx are updated to reflect the new location of the Speakers2023 and Speakers2024 components.
  • New Styling: A new styling file Speakers.style.ts was created to hold the styling for the Speakers component.

Changelog

Click here to see the changelog
  • src/App.tsx
    • Updated import paths for Speakers2023 (line 72) and Speakers2024 (line 95) to reflect the new directory structure.
    • The old import paths ./2023/Speakers/Speakers2023 and ./2024/Speakers/Speakers2024 were replaced with ./components/YearSpecific/Speakers/Speakers2023 and ./components/YearSpecific/Speakers/Speakers2024 respectively.
  • src/components/YearSpecific/Speakers/Speakers.style.ts
    • Created a new styling file for the Speakers component.
    • Includes styled components for the speakers section, icons, slash containers, slash text, wave container, and speaker cards container.
  • src/components/YearSpecific/Speakers/Speakers.tsx
    • Created a new Speakers component that takes year and webData as props.
    • This component fetches speaker data based on the provided year and renders the speaker cards.
    • Includes styling and layout for the speakers section, including title, subtitle, and speaker cards.
  • src/components/YearSpecific/Speakers/Speakers2023.tsx
    • Created a Speakers2023 component that renders the Speakers component with the year set to '2023' and imports the 2023 web data.
    • This component serves as a wrapper to pass the correct year and data to the common Speakers component.
  • src/components/YearSpecific/Speakers/Speakers2024.tsx
    • Created a Speakers2024 component that renders the Speakers component with the year set to '2024' and imports the 2024 web data.
    • This component serves as a wrapper to pass the correct year and data to the common Speakers component.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


A common ground we seek,
To banish code that's bleak,
Speakers rise as one,
Yearly battles done,
Elegance in code we speak.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

The pull request refactors the Speakers components to reduce code duplication by creating a generic Speakers component and year-specific wrappers. This is a good approach to improve maintainability and reduce redundancy. The changes look good overall, but there are a few minor suggestions for improvement.

Merge Readiness

The code changes effectively reduce code duplication and improve maintainability. I recommend merging this pull request after addressing the identified medium severity issue. I am unable to directly approve the pull request, and recommend that others review and approve this code before merging.

Copy link

sonarqubecloud bot commented Apr 1, 2025

Quality Gate Failed Quality Gate failed

Failed conditions
10.5% Coverage on New Code (required ≥ 75%)
71.9% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

Copy link

netlify bot commented Apr 1, 2025

Deploy Preview for dev-bcn failed.

Name Link
🔨 Latest commit 432142d
🔍 Latest deploy log https://app.netlify.com/sites/dev-bcn/deploys/67f8cfa86ea18900085ca18c

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.

1 participant