Refactor/postgrest api #5
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
…w for modern standards
🔄 Database Layer Refactor: - Migrated from Drizzle ORM to PostgREST for improved performance - Enhanced query optimization with PostgREST filtering - Maintained full TypeScript support throughout migration 👥 Improved Collaborator System: - Fixed collaborator visibility for both workspace owners and invitees - Added complete collaborator list including workspace owners - Implemented online status indicators with green dots - Enhanced avatar fallbacks for all collaborators - Added detailed tooltips with online status 🎨 UI/UX Enhancements: - Instant breadcrumb navigation visibility - Banner inheritance from workspace to folders/files - Real-time connection status indicators - Responsive collaborator list for mobile 🚀 Performance Optimizations: - Reduced re-rendering with optimized React hooks - Stable realtime connections with proper cleanup - Memory leak prevention for subscriptions - Reduced concurrent connection usage 🔧 Developer Experience: - Fixed all ESLint warnings and errors - Resolved TypeScript compilation issues - Better code organization and architecture - Enhanced error handling and user feedback 🐛 Bug Fixes: - Resolved dashboard redirect loop issues - Fixed deprecated Stripe payment session properties - Improved server-side authentication handling - Better file operation error handling 📚 Documentation: - Updated README.md with recent changes - Added comprehensive feature documentation - Included migration details and improvements
- Added realtime-dashboard.png screenshot to showcase the real-time editor - Enhanced visual documentation for better user understanding - Positioned screenshot prominently in the Real-time Editor section
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Added last updated timestamp: 2025-08-19 - Fixed GitHub sync issue with small change - Ensured repository is up to date
- Updated CI workflow to use Node.js 20 instead of 18 - Updated deploy workflow to use Node.js 20 instead of 18 - Added engines field to package.json specifying Node.js >=20.19.0 - Fixed NEXT_PUBLIC_SUPABASE_ANON_KEY environment variable reference - Added refactor/postgrest-api branch to CI triggers - Resolves [email protected] Node.js compatibility error
- Add unit tests for QuillEditor component (9 tests) - Add unit tests for DashboardPage component (7 tests) - Add unit tests for HomePage component (6 tests) - Add unit tests for utility functions (5 tests) - Configure Vitest with proper mocks and test environment - Fix async component testing issues - All 28 tests passing successfully - Maintain existing functionality while improving test coverage
- Add .coderabbit.yaml configuration for AI-powered code analysis - Add .coderabbit.ignore for excluded files and directories - Integrate CodeRabbit into existing CI workflow instead of separate workflow - Update README.md with CodeRabbit and Snyk security monitoring info - CodeRabbit will automatically review PRs when configured in repository - Maintains existing CI/CD pipeline while adding AI-powered code quality
- Fix Quill mock in quill-editor.test.tsx to properly handle register function - Add global Quill mock in vitest.setup.ts to prevent unhandled errors - All 28 tests now pass without Quill.register errors - GitHub Actions CI should now pass successfully - Maintains existing test functionality while fixing CI compatibility
- Replace createRouteHandlerClient with createClient from utils/server - Fix create-checkout-session API route to prevent build-time client creation - Fix create-portal-link API route to prevent build-time client creation - Build now completes successfully without Supabase configuration errors - Maintains existing functionality while fixing build compatibility - All 28 tests still pass successfully
- Replace fragile build-phase detection with graceful error handling - Implement environment-aware behavior (development vs production/build) - Add try-catch protection for cookies() and client creation - Return safe fallbacks during build to prevent failures - Maintain clear error messages in development mode - Build now succeeds reliably without NEXT_PHASE dependency - All 28 tests still pass successfully - More maintainable and future-proof approach
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.
I have refactor the project code to use supabase postgREST api instead of supabase database because supabase database url was having dns lookup issue. This leads to no communication with database via drizzle ORM. I ended fallback on PostgREST