Canary ✨ #7
Open
Canary ✨ #7
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
fix: prodd!!!
fix: add pre-production env to gitignore
fix: node-env to dev from prod
Update the callbackURL in the login.tsx file to use a better authentication method that automatically resolves the callback URL. The previous callbackURL was temporary and needed to be removed.
### TL;DR Redesigned the calendar sidebar to include a new user menu and streamlined calendar management interface. ### What changed? - Added a new UserMenu component with dropdown functionality - Moved calendar creation into the user menu dropdown - Simplified the calendar list view by removing visibility toggles - Relocated ServerAvailability component to the user menu - Added proper session handling and user authentication display - Renamed props in Calendar component for better clarity - Enhanced CreateCalendar component with loading states and toast notifications ### How to test? 1. Log in to the application 2. Verify user profile appears in the sidebar footer 3. Click the user menu to ensure dropdown displays correctly 4. Test calendar creation from the dropdown menu 5. Confirm toast notifications appear during calendar operations 6. Verify server availability status in the user menu 7. Test sign out functionality ### Why make this change? This redesign improves the user experience by consolidating user-related actions into a single menu and simplifying the calendar management interface. The changes make the application more intuitive while maintaining all essential functionality in a more organized structure.
### TL;DR Replaced custom proxy implementation with h3-proxy library for API and S3 endpoints. ### What changed? - Removed Firebase dependencies and added h3-proxy library - Created two middleware files for handling API and S3 proxying - Removed individual proxy route handlers in favor of middleware approach - Implemented path rewriting and filtering for both proxies ### How to test? 1. Make requests to `/api/meetingbaas/*` endpoints to verify API proxy functionality 2. Make requests to `/api/s3/*` endpoints to verify S3 proxy functionality 3. Verify that paths are correctly rewritten and forwarded to their respective target URLs 4. Confirm that all existing proxy functionality continues to work as expected ### Why make this change? Using h3-proxy provides a more maintainable and standardized approach to handling proxy requests. The library offers built-in features for path rewriting and filtering, reducing the amount of custom code needed while improving reliability and maintainability.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Canary