Skip to content

refactor: remove src directory and update config paths#21

Open
francescopausellii wants to merge 3 commits intomainfrom
refactor/architecture
Open

refactor: remove src directory and update config paths#21
francescopausellii wants to merge 3 commits intomainfrom
refactor/architecture

Conversation

@francescopausellii
Copy link
Contributor

@francescopausellii francescopausellii commented Mar 25, 2026

The PR introduces a cleaner and lighter starting architecture compared to the original src directory, and also moves the core authentication logic of better-auth to a more shared location

@gemini-code-assist
Copy link

Summary of Changes

Hello, 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!

This pull request streamlines the project's directory structure by eliminating the src folder, promoting a flatter file hierarchy. This change simplifies module resolution and path management throughout the codebase. Additionally, it centralizes authentication-related logic into a dedicated lib/auth directory, enhancing code organization and maintainability for authentication features.

Highlights

  • Directory Structure Refactor: The top-level src directory has been removed, flattening the project's file hierarchy and making the project root the primary reference point for modules.
  • Configuration Updates: Configuration files including .oxfmtrc.json, drizzle.config.ts, and tsconfig.json were updated to reflect the new file paths and alias mappings.
  • Import Path Adjustments: Numerous import statements across various files were updated to align with the new, flatter directory structure and consolidated lib/auth paths.
  • Authentication Module Reorganization: Authentication-related utility files, previously under src/features/auth/lib, have been consolidated into a new lib/auth directory for improved modularity.
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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

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

@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

This pull request primarily refactors import paths across the codebase, including updates to configuration files like .oxfmtrc.json, drizzle.config.ts, and tsconfig.json, reflecting a likely change in the project's directory structure and consolidation of authentication-related files. A critical performance issue was identified in app/page.tsx, where importing useSession from lib/auth/client.ts violates Rule 2.1 (bundle-barrel-imports) of the repository's style guide. This barrel file import can unnecessarily increase bundle size by including unused client-side authentication functions, and it is recommended to refactor for more granular imports to optimize tree-shaking.

Copy link
Contributor

@cecco25 cecco25 left a comment

Choose a reason for hiding this comment

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

  • Format vitest.config.mts
  • Update README to match current architecture

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