fix: resolve Card component padding/alignment, restore emptied compon…#156
Open
midexol wants to merge 3 commits into
Open
fix: resolve Card component padding/alignment, restore emptied compon…#156midexol wants to merge 3 commits into
midexol wants to merge 3 commits into
Conversation
…ents, fix library build & tests
|
@midexol Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
# Conflicts: # src/lib/adapter.ts
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
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.
Description
Standardizes the Card component properties and ref-forwarding, restores core component implementations that were commit-erased, and fixes the library compilation and test runner configurations.
Related Issues
Closes #103
Type of Change
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Documentation update
Testing
Describe how you tested your changes:
Ran npm run build to verify library ESM, CJS, and typescript declaration files compile successfully.
Ran npm run type-check to verify zero compile-time TypeScript errors.
Ran npx vitest run to verify all 239 unit tests in the project pass successfully.