Dev #431
Open
Dev #431
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
…riptions for Storybook, Git commit, and component writing guidelines
…nect links and enhancing font-display properties
…rify commit type descriptions
… improved type safety
…pe safety in utils
…erence' rule for flexibility
…prove error handling for invalid files
…rove documentation consistency
…port separate ESM and CJS formats, enhancing build flexibility and module preservation
…TypeScript support, integrate additional plugins, and improve rule management for better code quality and consistency
…on for automatic code formatting
…uild, preview, lint, and database scripts while removing outdated SolidStart content
…ts, improving error logging and consistency; modify gen-supabase-types script to use console.info for success messages; adjust import order in various components for better readability; enhance focus controller utilities and tests for improved focus management; streamline cookie utility imports and remove unused storage-key file
…to id-length exceptions, disable 'unicorn/import-style' rule, and include '*.spec.tsx' in test file patterns for improved linting flexibility
…ation guidelines, detailing project structure, coding standards, error handling, testing, and best practices for improved clarity and consistency
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
…ing dynamic import parameter and directly importing the Pretendard CSS file for improved clarity and performance
…t, ensuring a clean environment for end-to-end tests
…directory for better log management
…mport handling by Vite for improved understanding
…g stricter environment variable validation
…g Playwright configuration for dynamic port handling, and refining app configuration comments for clarity
…, outlining refactoring suggestions, type safety improvements, and code quality enhancements
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.
Note
Introduces a new SolidStart app and modernizes tooling while removing the legacy client.
apps/coong— SolidStart SSR/SPA config, Supabase integration (@supabase/ssr,supabase-js), Drizzle ORM with migrations and RLS SQL, UnoCSS, service worker generation, environment setup, and Playwright E2E harness (mockable Supabase via middleware)apps/bplan-client— Deletes the old app and its components, routes, TRPC, and build configapps/bichi— Minimal SolidStart app setup with UnoCSS and devtoolsapps/coongand packages, preview defaults, and Vite config tweaksoxlintrules, Prettier moved to YAML with updated options,.gitignore/.vscodeadditions, PWA assets config, scripts for Supabase types and E2E, and MCP server set tosupabaseWritten by Cursor Bugbot for commit 90a2964. This will update automatically on new commits. Configure here.