#3 feat: Dashboard UI 구현 #8
Conversation
|
Caution Review failedThe pull request is closed. WalkthroughThis update introduces a new Dashboard feature, including several React components for displaying course and schedule information. The routing configuration is updated to render the Dashboard as the default view for both student and admin paths. Supporting type definitions, SVG assets, and CSS variables are also added or modified. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant App
participant Layout
participant Dashboard
participant CourseList
participant ScheduleList
User->>App: Navigate to /student or /admin
App->>Layout: Render layout for route
Layout->>Dashboard: Render Dashboard as index route
Dashboard->>CourseList: Render course list
Dashboard->>ScheduleList: Render schedule list
Estimated code review effort3 (~45 minutes) Possibly related PRs
Suggested reviewers
Poem
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
npm error Exit handler never called! 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (6)
src/pages/common/Dashboard.tsx (1)
4-16: Consider responsive design and header position adjustments.The Dashboard component structure is clean and well-organized. However, consider these improvements:
- Responsive Design: The fixed width
w-289might not work well on all screen sizes- Header Position: As mentioned in the PR objectives, layout adjustments may be needed for the modified header position
Consider this responsive improvement:
- <div className='min-h-screen h-full py-10 bg-background flex-col'> - <div className='w-289 mx-auto my-0'> + <div className='min-h-screen h-full py-10 bg-background flex-col'> + <div className='max-w-289 w-full mx-auto my-0 px-4'>This maintains the maximum width while allowing flexibility on smaller screens.
src/assets/svg/EllipsisIcon.tsx (1)
1-15: SVG component implementation looks good, consider making fill color customizable.The component follows the established svgr pattern correctly with proper TypeScript typing and props spreading for customization. The SVG structure and positioning are appropriate for an ellipsis icon.
Consider making the fill color customizable by removing the hardcoded
#7D7993and allowing it to be overridden via props:- <circle cx={3.305} cy={3.198} r={2.5} fill='#7D7993' /> - <circle cx={11.402} cy={3.198} r={2.5} fill='#7D7993' /> - <circle cx={19.5} cy={3.198} r={2.5} fill='#7D7993' /> + <circle cx={3.305} cy={3.198} r={2.5} fill='currentColor' /> + <circle cx={11.402} cy={3.198} r={2.5} fill='currentColor' /> + <circle cx={19.5} cy={3.198} r={2.5} fill='currentColor' />This would allow the icon to inherit the text color from its parent, making it more flexible for different UI contexts.
src/components/common/Dashboard/ScheduleCard.tsx (1)
8-8: Consider making the card width responsive.The hardcoded width of
396pxmight cause layout issues on different screen sizes. Consider using responsive width classes or making it configurable via props.- <div className='flex items-start p-7 gap-6 border-0 bg-white w-[396px] mb-5 rounded-3xl'> + <div className='flex items-start p-7 gap-6 border-0 bg-white w-full max-w-[396px] mb-5 rounded-3xl'>src/components/common/Dashboard/CourseList.tsx (1)
38-43: Consider consistent button styling.The "추가" button has explicit styling while the "더보기" button inherits default styles. Consider making the styling consistent:
- <button className='bg-white border-0 px-3 py-0.5 rounded-[10px]'> - + 추가 - </button> - <button>더보기</button> + <button className='bg-white border-0 px-3 py-0.5 rounded-[10px]'> + + 추가 + </button> + <button className='bg-white border-0 px-3 py-0.5 rounded-[10px]'> + 더보기 + </button>src/components/common/Dashboard/CourseCard.tsx (1)
22-22: Remove unused debugging line.The line
props.semester;appears to be leftover debugging code and should be removed.- props.semester;src/components/common/Dashboard/ScheduleList.tsx (1)
6-51: Consider addressing the color criteria for remaining days mentioned in PR objectives.The mock data currently assigns the same
remainingDaysvalue to all assignments within a schedule, but the PR objectives mention a discussion point about "criteria for changing the color of the remaining days label (whether it changes only one day before or only for the most recent item)."The current implementation doesn't include color variation logic for the remaining days. Consider implementing this feature or adding a TODO comment to track this requirement.
Would you like me to help implement the color criteria logic for the remaining days label based on the discussion points in the PR objectives?
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
public/svg/ellipsisIcon.svgis excluded by!**/*.svg
📒 Files selected for processing (10)
src/App.tsx(2 hunks)src/assets/svg/EllipsisIcon.tsx(1 hunks)src/assets/svg/index.ts(1 hunks)src/components/common/Dashboard/CourseCard.tsx(1 hunks)src/components/common/Dashboard/CourseList.tsx(1 hunks)src/components/common/Dashboard/ScheduleCard.tsx(1 hunks)src/components/common/Dashboard/ScheduleList.tsx(1 hunks)src/components/common/Dashboard/types.ts(1 hunks)src/index.css(1 hunks)src/pages/common/Dashboard.tsx(1 hunks)
🧰 Additional context used
🧠 Learnings (10)
📓 Common learnings
Learnt from: JiiminHa
PR: 2025-snowCode/snowCode-Client#2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
Learnt from: JiiminHa
PR: 2025-snowCode/snowCode-Client#6
File: src/App.tsx:6-11
Timestamp: 2025-07-16T12:33:43.839Z
Learning: JiiminHa prefers hierarchical routing structure with role-based path organization: common routes at root level (/), student-specific routes under /student prefix, and admin-specific routes under /admin prefix, using nested routes with a shared Layout component for consistent UI patterns.
src/assets/svg/index.ts (1)
Learnt from: suminb99
PR: 2025-snowCode/snowCode-Client#6
File: src/assets/svg/ChatIcon.tsx:14-14
Timestamp: 2025-07-16T13:14:38.797Z
Learning: In this project, the svgr workflow requires placing original SVG files in the `public/svg` folder first, then running `npm run svgr` command to generate converted TSX files in the `src/assets/svg` folder according to the root configuration.
src/assets/svg/EllipsisIcon.tsx (3)
Learnt from: suminb99
PR: 2025-snowCode/snowCode-Client#6
File: src/assets/svg/ChatIcon.tsx:14-14
Timestamp: 2025-07-16T13:00:01.888Z
Learning: This project uses svgr for automatic SVG to React component conversion. Running `npm run svgr` automatically converts all svgr files to React component format and handles camelCase conversion for SVG attributes (e.g., stroke-width → strokeWidth).
Learnt from: suminb99
PR: 2025-snowCode/snowCode-Client#6
File: src/assets/svg/ChatIcon.tsx:14-14
Timestamp: 2025-07-16T13:14:38.797Z
Learning: In this project, the svgr workflow requires placing original SVG files in the `public/svg` folder first, then running `npm run svgr` command to generate converted TSX files in the `src/assets/svg` folder according to the root configuration.
Learnt from: JiiminHa
PR: 2025-snowCode/snowCode-Client#2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
src/pages/common/Dashboard.tsx (1)
Learnt from: JiiminHa
PR: 2025-snowCode/snowCode-Client#2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
src/App.tsx (2)
Learnt from: JiiminHa
PR: 2025-snowCode/snowCode-Client#2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
Learnt from: JiiminHa
PR: 2025-snowCode/snowCode-Client#6
File: src/App.tsx:6-11
Timestamp: 2025-07-16T12:33:43.839Z
Learning: JiiminHa prefers hierarchical routing structure with role-based path organization: common routes at root level (/), student-specific routes under /student prefix, and admin-specific routes under /admin prefix, using nested routes with a shared Layout component for consistent UI patterns.
src/components/common/Dashboard/ScheduleCard.tsx (1)
Learnt from: JiiminHa
PR: 2025-snowCode/snowCode-Client#2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
src/components/common/Dashboard/CourseList.tsx (1)
Learnt from: JiiminHa
PR: 2025-snowCode/snowCode-Client#2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
src/components/common/Dashboard/CourseCard.tsx (1)
Learnt from: JiiminHa
PR: 2025-snowCode/snowCode-Client#2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
src/components/common/Dashboard/ScheduleList.tsx (1)
Learnt from: JiiminHa
PR: 2025-snowCode/snowCode-Client#2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
src/components/common/Dashboard/types.ts (1)
Learnt from: JiiminHa
PR: 2025-snowCode/snowCode-Client#2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
🧬 Code Graph Analysis (2)
src/components/common/Dashboard/ScheduleCard.tsx (1)
src/components/common/Dashboard/types.ts (1)
Assignment(26-26)
src/components/common/Dashboard/CourseCard.tsx (1)
src/components/common/Dashboard/types.ts (1)
Course(26-26)
🔇 Additional comments (13)
src/index.css (1)
47-47: LGTM! Color variable addition follows established patterns.The new
--color-grayvariable is properly placed within the @theme block and follows the existing naming convention. The light gray color (#f9f9f9) is appropriate for UI elements in the Dashboard components.src/components/common/Dashboard/types.ts (1)
1-27: Excellent TypeScript interface design!The type definitions are well-structured with clear separation of concerns:
Scheduleproperly referencesAssignment[]creating a good relationship- All interfaces use appropriate primitive types
- Property names are descriptive and follow consistent naming conventions
- The
export typesyntax is correctly usedThis aligns with the project's preference for TypeScript interfaces providing clear structure and type safety.
src/assets/svg/index.ts (1)
4-5: EllipsisIcon follows svgr workflow and exports are correctVerified that
public/svg/ellipsisIcon.svgexists andsrc/assets/svg/EllipsisIcon.tsxwas generated accordingly. The SVG export ordering remains alphabetical and consistent.src/App.tsx (2)
3-3: Good import path convention.The Dashboard import follows the established relative path pattern and is placed appropriately with other imports.
17-17: Excellent routing implementation aligns with established patterns.The index routes for both
/studentand/adminpaths perfectly match the hierarchical routing structure preference. Using the same Dashboard component for both roles makes sense for common functionality while maintaining the role-based path organization.Also applies to: 23-23
src/pages/common/Dashboard.tsx (2)
1-2: Clean component imports following established patterns.The relative imports are properly structured and follow the project's component organization.
9-12: Well-structured layout with clear component separation.The flex layout properly separates CourseList and ScheduleList components, making the dashboard easy to understand and maintain.
src/components/common/Dashboard/ScheduleCard.tsx (1)
14-16: Text truncation implementation addresses the PR discussion point.The use of
truncateclass for the assignment name effectively handles long text by showing ellipsis, which is a good solution for the text handling discussion point raised in the PR objectives. This maintains consistent card height while ensuring readability.src/components/common/Dashboard/CourseList.tsx (1)
5-28: Mock data structure is well-organized for UI verification.The hardcoded course data serves its purpose for UI verification as mentioned in the PR objectives. The data structure includes all necessary fields for the CourseCard component.
src/components/common/Dashboard/CourseCard.tsx (2)
6-19: Semester conversion function is well-implemented.The
getSemesterNumberfunction properly handles the semester string conversion with appropriate Korean translations for summer/winter terms and includes a sensible default case.
24-51: Card layout structure is well-organized.The two-section layout effectively separates course information from the action button and statistics, creating a clean and readable interface.
src/components/common/Dashboard/ScheduleList.tsx (2)
54-59: Date formatting function is clean and effective.The
changeDateFormatfunction properly converts Date objects to the desired "mm.dd" format with appropriate handling of single-digit months and days.
70-90: Conditional rendering creates good visual hierarchy.The conditional rendering logic effectively distinguishes between the first assignment (with date marker) and subsequent assignments (indented), creating a clear visual hierarchy for grouped schedules.
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (2)
src/components/common/Dashboard/CourseList.tsx (1)
43-50: Improve conditional rendering with null instead of empty string.The conditional rendering logic is correct, but using
nullinstead of an empty string is more idiomatic in React.{userType === 'admin' ? ( <button className='bg-white border-0 px-3 py-1 rounded-[10px] flex-center gap-[6px] text-base font-medium text-secondary-black'> <AddIcon width={12} height={12} /> <span>추가</span> </button> - ) : ( - '' - )} + ) : null}src/components/common/Dashboard/CourseCard.tsx (1)
46-52: Improve conditional rendering with null instead of empty string.Similar to the CourseList component, using
nullinstead of an empty string is more idiomatic in React for conditional rendering.{userType === 'admin' ? ( <button className='absolute right-8'> <EllipsisIcon width={21.2} height={5} /> </button> - ) : ( - '' - )} + ) : null}
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (5)
src/components/common/Dashboard/CourseCard.tsx(1 hunks)src/components/common/Dashboard/CourseList.tsx(1 hunks)src/components/common/Dashboard/ScheduleCard.tsx(1 hunks)src/components/common/Dashboard/types.ts(1 hunks)src/pages/common/Dashboard.tsx(1 hunks)
🧠 Learnings (4)
📓 Common learnings
Learnt from: JiiminHa
PR: 2025-snowCode/snowCode-Client#2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
Learnt from: JiiminHa
PR: 2025-snowCode/snowCode-Client#6
File: src/App.tsx:6-11
Timestamp: 2025-07-16T12:33:43.867Z
Learning: JiiminHa prefers hierarchical routing structure with role-based path organization: common routes at root level (/), student-specific routes under /student prefix, and admin-specific routes under /admin prefix, using nested routes with a shared Layout component for consistent UI patterns.
src/components/common/Dashboard/CourseList.tsx (1)
Learnt from: JiiminHa
PR: #2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
src/components/common/Dashboard/types.ts (1)
Learnt from: JiiminHa
PR: #2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
src/components/common/Dashboard/CourseCard.tsx (1)
Learnt from: JiiminHa
PR: #2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
🧬 Code Graph Analysis (1)
src/components/common/Dashboard/CourseList.tsx (1)
src/components/common/Dashboard/types.ts (2)
Course(28-28)UserType(28-28)
🚧 Files skipped from review as they are similar to previous changes (2)
- src/pages/common/Dashboard.tsx
- src/components/common/Dashboard/ScheduleCard.tsx
🧰 Additional context used
🧠 Learnings (4)
📓 Common learnings
Learnt from: JiiminHa
PR: 2025-snowCode/snowCode-Client#2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
Learnt from: JiiminHa
PR: 2025-snowCode/snowCode-Client#6
File: src/App.tsx:6-11
Timestamp: 2025-07-16T12:33:43.867Z
Learning: JiiminHa prefers hierarchical routing structure with role-based path organization: common routes at root level (/), student-specific routes under /student prefix, and admin-specific routes under /admin prefix, using nested routes with a shared Layout component for consistent UI patterns.
src/components/common/Dashboard/CourseList.tsx (1)
Learnt from: JiiminHa
PR: #2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
src/components/common/Dashboard/types.ts (1)
Learnt from: JiiminHa
PR: #2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
src/components/common/Dashboard/CourseCard.tsx (1)
Learnt from: JiiminHa
PR: #2
File: src/components/Header/StudentHeader.tsx:10-10
Timestamp: 2025-07-13T00:27:31.464Z
Learning: Using TypeScript interfaces for React component props (like StudentHeaderProps) provides clear structure, improves readability, and makes components more maintainable and extensible for future development.
🧬 Code Graph Analysis (1)
src/components/common/Dashboard/CourseList.tsx (1)
src/components/common/Dashboard/types.ts (2)
Course(28-28)UserType(28-28)
🔇 Additional comments (7)
src/components/common/Dashboard/types.ts (1)
1-28: Well-structured TypeScript definitions for Dashboard feature.The type definitions are comprehensive and well-organized. The
UserTypeunion type clearly distinguishes between user roles, and the interfaces provide strong typing for the Dashboard components. This aligns with the preference for TypeScript interfaces to improve code structure and maintainability.src/components/common/Dashboard/CourseList.tsx (3)
6-29: Mock data structure aligns well with Course interface.The hardcoded course data properly matches the
Courseinterface definition and provides good test data for UI development. The data structure is comprehensive and realistic.
31-33: Well-defined props interface following TypeScript best practices.The
CourseListPropsinterface correctly extends the component's typing requirements and aligns with the preference for using TypeScript interfaces for React component props.
53-55: Correct use of key prop and spread operator for course data.The mapping logic properly uses the course ID as the key and spreads the course properties to the CourseCard component. The userType prop is correctly passed down.
src/components/common/Dashboard/CourseCard.tsx (3)
4-6: Well-structured props interface extending Course type.The
CourseCardPropsinterface correctly extends theCourseinterface and adds theuserTypeproperty, following TypeScript best practices for component props.
35-44: Well-structured course information display.The course information section properly displays the formatted semester, year, section, title, and description with appropriate styling and text hierarchy.
53-62: Clean layout for unit and assignment count display.The statistics section effectively displays unit count and assignment count with proper visual separation and formatting.
| const getSemesterNumber = (semester: string): string => { | ||
| switch (semester) { | ||
| case 'FIRST': | ||
| return '1'; | ||
| case 'SUMMER': | ||
| return '여름'; | ||
| case 'SECOND': | ||
| return '2'; | ||
| case 'WINTER': | ||
| return '겨울'; | ||
| default: | ||
| return 'unknown'; | ||
| } | ||
| }; |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Remove unsupported 'WINTER' case from semester mapping.
The getSemesterNumber function includes a 'WINTER' case, but the Course interface in types.ts only defines semester as 'FIRST' | 'SECOND' | 'SUMMER'. This creates an inconsistency.
const getSemesterNumber = (semester: string): string => {
switch (semester) {
case 'FIRST':
return '1';
case 'SUMMER':
return '여름';
case 'SECOND':
return '2';
- case 'WINTER':
- return '겨울';
default:
return 'unknown';
}
};📝 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.
| const getSemesterNumber = (semester: string): string => { | |
| switch (semester) { | |
| case 'FIRST': | |
| return '1'; | |
| case 'SUMMER': | |
| return '여름'; | |
| case 'SECOND': | |
| return '2'; | |
| case 'WINTER': | |
| return '겨울'; | |
| default: | |
| return 'unknown'; | |
| } | |
| }; | |
| const getSemesterNumber = (semester: string): string => { | |
| switch (semester) { | |
| case 'FIRST': | |
| return '1'; | |
| case 'SUMMER': | |
| return '여름'; | |
| case 'SECOND': | |
| return '2'; | |
| default: | |
| return 'unknown'; | |
| } | |
| }; |
🤖 Prompt for AI Agents
In src/components/common/Dashboard/CourseCard.tsx between lines 8 and 21, remove
the 'WINTER' case from the getSemesterNumber function to align with the Course
interface in types.ts, which only supports 'FIRST', 'SECOND', and 'SUMMER'
semesters. Adjust the switch statement to exclude 'WINTER' and ensure the
default case handles any unexpected values.
⚙️ Related ISSUE Number
Related #3
📄 Work Description
CourseList, CourseCard, ScheduleList, ScheduleCard컴포넌트 개발components/common/Dashboard,pages/common/Dashboard.tsx)/student, /admin경로의 기본 페이지로 대시보드 페이지 설정)📷 Screenshot
Screen.Recording.2025-07-23.at.22.20.45.mov
💬 To Reviewers
머지 전 수정 / 추가 구현 필요한 부분:
아래 두 항목은 논의가 필요할 것 같습니다!
🔗 Reference
Summary by CodeRabbit
Summary by CodeRabbit
New Features
Style
Documentation