refac: dirs

[deewakar-k]

What did you ship?

Fixes:

• [ ] #XXX (GitHub issue number)
• [ ] MAR-XXX (Linear issue number - should be visible at the bottom of the GitHub issue description)

Checklist:

• [ ] I have self-reviewed the code (A decent size PR without self-review might be rejected)
• [ ] I pinky swear that my codes gonna work as I have testing every possible scenario.
• [ ] I ignored Coderabbit suggestion because it does not make any sense.
• [ ] I took Coderabbit suggestion under consideration as some of it makes sense.
• [ ] I have commented my code, particularly in hard-to-understand areas.

OR:

• [ ] shut up and let me cook.

[coderabbitai[bot]]

📝 Walkthrough

📝 Walkthrough

## Walkthrough This pull request involves the removal of several React components, specifically a custom select dropdown and an inbox text area, from the frontend application. Additionally, multiple components have updated import paths for a utility function, changing from a relative path to an absolute path. The functionality of the remaining components is preserved despite these changes. ## Changes | File Path | Change Summary | |------------------------------------------------|---------------------------------------------------------------------------------------------------| | apps/frontend/components/ui/select.tsx | Component removed: `Select`, `SelectGroup`, `SelectValue`, `SelectTrigger`, `SelectScrollUpButton`, `SelectScrollDownButton`, `SelectContent`, `SelectLabel`, `SelectItem`, `SelectSeparator`. | | apps/frontend/src/components/Dropdown/Dropdown.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. | | apps/frontend/src/components/Icon.tsx | Import path updated for `cn` from `../../lib/utils` to `@/src/utils/utils`. | | apps/frontend/src/components/Inbox/RescheduleCalendar/Calendar.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. Component exported: `Calendar`. | | apps/frontend/src/components/InboxTextArea.tsx | Component removed: `InboxTextArea`. | | apps/frontend/src/components/Skeleton.tsx | Import path updated for `cn` from `@/lib/utils` to `../utils/utils`. | | apps/frontend/src/components/Surface.tsx | Import path updated for `cn` from `../../lib/utils` to `@/src/utils/utils`. | | apps/frontend/src/components/TodayMeetings.tsx | Component removed: `TodayMeetings`. | | apps/frontend/src/components/atoms/Select.tsx | Import path updated for `Select` and related components from `"./ui/select"` to `"../ui/select"`. | | apps/frontend/src/components/atoms/Switch.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. | | apps/frontend/src/components/atoms/Tooltip.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. | | apps/frontend/src/components/ui/button.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. | | apps/frontend/src/components/ui/calendar.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. Component exported: `Calendar`. | | apps/frontend/src/components/ui/card.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. | | apps/frontend/src/components/ui/context-menu.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. | | apps/frontend/src/components/ui/dialog.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. | | apps/frontend/src/components/ui/dropdown.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. | | apps/frontend/src/components/ui/input.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. | | apps/frontend/src/components/ui/popover.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. | | apps/frontend/src/components/ui/select.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. | | apps/frontend/src/components/ui/textarea.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. | | apps/frontend/src/components/ui/toast.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. | | apps/frontend/src/extensions/SlashCommand/MenuList.tsx | Import path updated for `cn` from `@/lib/utils` to `@/src/utils/utils`. | ## Possibly related PRs - **#397**: The main PR involves the deletion of a custom select dropdown component, while this PR introduces a new controller function for fetching items based on date ranges, which may relate to how items are displayed or selected in the UI. - **#424**: The main PR's changes to the UI components may relate to this PR's introduction of a text editor for expanded item views, as both involve user interaction with item details. - **#518**: The main PR's focus on item management aligns with this PR's enhancements to the `InboxItems` component, particularly regarding item rescheduling and state management. - **#519**: The main PR's changes to item display and management are relevant to this PR's modifications to the item fetching logic based on date ranges. - **#581**: The main PR's updates to the item expand modal component are directly related to this PR's focus on enhancing the modal functionality for inbox and other views. - **#594**: The main PR's changes to the reading list interface may connect with this PR's updates to the `AddItemForm` and `ItemsList` components, both of which involve user input and item management. - **#598**: The main PR's modifications to the GitHub login functionality may relate to this PR's updates in the `GithubLogin` component, focusing on improving the login process. - **#614**: The main PR's restoration of previous changes may connect with this PR's focus on reverting a prior revert, indicating ongoing adjustments to the reading list feature. - **#574**: The main PR's refactoring of onboarding components may relate to this PR's updates to the onboarding process, enhancing user experience and component organization. > 🐰 In the meadow, changes bloom, > With dropdowns gone, there's more room. > Paths now clear, imports anew, > Components dance, in fresh view. > Hops of joy, as we refine, > Code so neat, it’s simply divine! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.