-
Notifications
You must be signed in to change notification settings - Fork 0
Release v1.0.0 - Initial release #38
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Refactor: Separate rows render logic and implement RowGroup component
…ructure Refactor: Update repo folder structure
* feat: Implement sortable functionality in MultiLevelTable component - Added `sortable` prop to MultiLevelTable and TableHeader components. - Introduced custom sorting logic for the 'Status' column. - Updated styles to indicate sortable columns with a pointer cursor. - Enhanced table header to conditionally render sorting indicators based on column state. * refactor: Move sort types to constant * fix: Fix lint errors * feat: Accept custom sort icons
* feat: Add style changes for filter * feat: Add changes for custom expand button
- Removed defaultThemeProps and integrated theme properties directly into the theme structure. - Updated MultiLevelTable and TableRow components to utilize the new theme structure with levelColors for row backgrounds. - Enhanced row styling logic in TableRow component using useMemo for performance optimization. - Changed package name in package-lock.json to reflect the correct organization.
* feat: Unit test setup * test: Add unit tests for TableRow, Pagination, and TableHeader components - Introduced unit tests for TableRow component, covering rendering, expansion, and custom rendering. - Added tests for Pagination component, validating navigation and page size changes. - Implemented tests for TableHeader component, ensuring correct rendering and filtering functionality. - Included necessary imports and mock data for testing. * feat: Add unit tests for SortType and defaultTheme - Introduced unit tests for the SortType enum, verifying its values and count. - Added tests for the defaultTheme structure, ensuring it contains the correct properties and valid configuration values for colors, table, pagination, and expand icon. - Updated vitest configuration to include test files with .ts and .tsx extensions. - Added @vitest/coverage-v8 dependency for improved test coverage reporting. * test: Add unit tests for MultiLevelTable component - Introduced comprehensive unit tests for the MultiLevelTable component, covering rendering, row expansion, sorting, pagination, custom theming, and filtering functionalities. - Validated the correct application of custom styles and rendering for status cells and pagination controls. - Ensured that the component behaves as expected with mock data and various configurations. --------- Co-authored-by: anitta-keyvalue <[email protected]>
* feat: Unit test setup * test: Add unit tests for TableRow, Pagination, and TableHeader components - Introduced unit tests for TableRow component, covering rendering, expansion, and custom rendering. - Added tests for Pagination component, validating navigation and page size changes. - Implemented tests for TableHeader component, ensuring correct rendering and filtering functionality. - Included necessary imports and mock data for testing. * feat: Add unit tests for SortType and defaultTheme - Introduced unit tests for the SortType enum, verifying its values and count. - Added tests for the defaultTheme structure, ensuring it contains the correct properties and valid configuration values for colors, table, pagination, and expand icon. - Updated vitest configuration to include test files with .ts and .tsx extensions. - Added @vitest/coverage-v8 dependency for improved test coverage reporting. * test: Add unit tests for MultiLevelTable component - Introduced comprehensive unit tests for the MultiLevelTable component, covering rendering, row expansion, sorting, pagination, custom theming, and filtering functionalities. - Validated the correct application of custom styles and rendering for status cells and pagination controls. - Ensured that the component behaves as expected with mock data and various configurations. * chore: Update test configuration and add coverage reporting - Added coverage reporting configuration to vitest for improved test insights. - Updated .gitignore to exclude coverage directory. - Enhanced App component with a data-testid for easier testing. - Introduced unit tests for the App component, validating rendering, theme toggling, and status cell colors. - Added tests for index exports to ensure correct component and type exports. - Created main test to verify App component rendering in strict mode. --------- Co-authored-by: anitta-keyvalue <[email protected]>
* refactor: Enhance MultiLevelTable structure and styling - Updated MultiLevelTable component to improve readability and maintainability by restructuring code and formatting. - Introduced a new wrapper for the table to handle overflow and ensure proper styling. - Added CSS rules to prevent cell content from wrapping and enhance table responsiveness. - Refactored rendering logic for pagination and table body for better separation of concerns. * Fix: Update test case
- Removed `allowImportingTsExtensions` and `noEmit` options from tsconfig.json for cleaner configuration. - Changed `MultiLevelTableProps` interface to be exported, allowing for better accessibility in other modules.
* feat: Add row selection functionality to MultiLevelTable * fix: Review comment fix
* feat: Add onRowClick feature * feat: Accept react node as column header
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.