chore: rename dashboard, marketing, and website components to kebab-case - #106
Merged
Conversation
- Standardize component naming conventions across modules. - Fix broken internal imports and clean up unused code in the bar chart component. - Update wrangler-generated worker configuration types.
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
This PR normalizes component file naming structures across the$\rightarrow$ $\rightarrow$
dashboard,marketing, andwebsitemodules. File names have been migrated from dot-separated and inconsistent naming styles to a clean, standard kebab-case format (e.g.,dashboard.stats.tsxstats.tsx,features.card.tsxfeature-card.tsx).Additionally, this PR handles necessary codebase cleanup by removing unused directives, fixing all broken internal relative imports, and committing the freshly regenerated Wrangler runtime configuration environment types.
Fixes #
🧪 Type of Change
🛠️ How Has This Been Tested?
Verified that application build succeeds with zero module resolution or TypeScript configuration path issues.
Executed the local Vitest suite to ensure relocated test files (
stats.test.tsx) execute natively and pass successfully.Verified that the Astro application initializes perfectly with the updated Cloudflare D1 and asset type declarations.
Unit/Integration tests added/passed
Local manual edge verification successful
📸 Screenshots / Diffs (if applicable)
✅ Checklist