Ran oxc (https://oxc.rs/docs/guide/usage/linter.html#vscode-extension) and fixed all the issues that came up, set it up to run as a PR check and added steps to the README.md asking users to use it.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
* **New Features**
* Introduced JavaScript linting using oxlint in development guidelines and CI workflow for improved code quality.
* Added oxlint configuration and dependencies to the project.
* **Bug Fixes**
* Improved error logging in various components and utilities for better debugging.
* Enhanced React list rendering by updating keys to use unique values instead of array indices, reducing rendering issues.
* Replaced browser alerts with toast notifications for a smoother user experience.
* **Refactor**
* Simplified component logic and state management by removing unused code, imports, props, and components across multiple files.
* Updated function and component signatures for clarity and maintainability.
* Improved efficiency of certain operations by switching from arrays to sets for membership checks.
* **Chores**
* Cleaned up and reorganized import statements throughout the codebase.
* Removed deprecated files, components, and middleware to streamline the codebase.
* **Documentation**
* Updated contribution guidelines to include linting requirements for code submissions.
* **Style**
* Minor formatting and readability improvements in JSX and code structure.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
# READ CAREFULLY THEN REMOVE
Remove bullet points that are not relevant.
PLEASE REFRAIN FROM USING AI TO WRITE YOUR CODE AND PR DESCRIPTION. IF YOU DO USE AI TO WRITE YOUR CODE PLEASE PROVIDE A DESCRIPTION AND REVIEW IT CAREFULLY. MAKE SURE YOU UNDERSTAND THE CODE YOU ARE SUBMITTING USING AI.
- Pull requests that do not follow these guidelines will be closed without review or comment.
- If you use AI to write your PR description your pr will be close without review or comment.
- If you are unsure about anything, feel free to ask for clarification.
## Description
Please provide a clear description of your changes.
---
## Type of Change
Please delete options that are not relevant.
- [ ] 🐛 Bug fix (non-breaking change which fixes an issue)
- [ ] ✨ New feature (non-breaking change which adds functionality)
- [ ] 💥 Breaking change (fix or feature with breaking changes)
- [ ] 📝 Documentation update
- [ ] 🎨 UI/UX improvement
- [ ] 🔒 Security enhancement
- [ ] ⚡ Performance improvement
## Areas Affected
Please check all that apply:
- [ ] Email Integration (Gmail, IMAP, etc.)
- [ ] User Interface/Experience
- [ ] Authentication/Authorization
- [ ] Data Storage/Management
- [ ] API Endpoints
- [ ] Documentation
- [ ] Testing Infrastructure
- [ ] Development Workflow
- [ ] Deployment/Infrastructure
## Testing Done
Describe the tests you've done:
- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] Manual testing performed
- [ ] Cross-browser testing (if UI changes)
- [ ] Mobile responsiveness verified (if UI changes)
## Security Considerations
For changes involving data or authentication:
- [ ] No sensitive data is exposed
- [ ] Authentication checks are in place
- [ ] Input validation is implemented
- [ ] Rate limiting is considered (if applicable)
## Checklist
- [ ] I have read the [CONTRIBUTING](../CONTRIBUTING.md) document
- [ ] My code follows the project's style guidelines
- [ ] I have performed a self-review of my code
- [ ] I have commented my code, particularly in complex areas
- [ ] I have updated the documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix/feature works
- [ ] All tests pass locally
- [ ] Any dependent changes are merged and published
## Additional Notes
Add any other context about the pull request here.
## Screenshots/Recordings
Add screenshots or recordings here if applicable.
---
_By submitting this pull request, I confirm that my contribution is made under the terms of the project's license._
* feat: Integrate Google OAuth and SWR for mail threads
* refactor: simplify mail list and navigation UI
* feat: enhance mail parsing and UI with sender details and unread status
* chore: update pnpm lock with new dependencies
* refactor: organize imports in app-sidebar component
* dynamic rendering data
* chore: update .gitignore with IDE-specific exclusions
* refactor(mail): update routing and component structure for mail views
* refactor(mail): remove draft and junk routes; update folder names to proper terms in UI and API
* refactor(mail): clean up imports, adjust API endpoints, and improve mail component structures for better clarity and performance
* automatic search
* YOP!
* KIND OF lint. lmao.
* feat:gmail connection WIP
* feat(mail): add mail count endpoint and dynamic sidebar stats
* feat(mail): add sanitization and dynamic provider support for email rendering
* grim's changes
* feat(mail): implement indexedDB caching for email threads and improve SWR configuration in layout component
* feat(mail): enhance indexedDB operations for email threads caching and update SWR configuration for better data handling
* idk
* fix(mail): adjust email body processing and reverse cached email messages for consistent order
* Fullscreen (#154)
* FULL SCREEN!!! RAH!!!
* Update mail-display.tsx
* auth
* email dispaly
* gmail connection
* env example resend add
* fix: env issues
* refactor: replace nanoid with randomUUID for ID generation in early access and update database schema to unify connection table
* refactor: update API endpoint for email connections and modify driver initialization for async support across mail routes
* feat: enhance Gmail OAuth flow and connection handling
- Update Google OAuth driver with expanded scopes and improved token management
- Modify callback route to handle user info extraction and connection creation more robustly
- Add unique constraint to email in connection table
- Improve error handling and logging in authentication process
* fix: improve error responses and connection handling in Gmail integration
- Enhance error messages when tokens or emails are missing.
- Update handling of Gmail connections in the API and user-related components
* feat: add default connection support and improve connection switching
- Add `defaultConnectionId` to user schema
- Implement PUT endpoint to set default connection for a user
- Update mail API routes to use dynamic provider and connection ID
- Enhance NavUser component with account switching functionality
- Modify hooks and auth logic to support default connection selection
* typo
* feat: integrate thread hook for email data loading in MailDisplay component
- Replace local email data state with useThread hook for improved loading management
* fix: improve mail route authorization with connection validation
- Add explicit check for connectionId in session
- Update database query to filter by both userId and connectionId
- Make connectionId optional in ParsedMessage type to support flexible connection handling
* privacy and tos
* linting
---------
Co-authored-by: Aj Wazzan <x_1337@outlook.com>
Co-authored-by: grim <75869731+vys69@users.noreply.github.com>
Co-authored-by: BlankParticle <blankparticle@gmail.com>
