marchhq / march

building a second brain for next generation makers;
GNU General Public License v3.0
41 stars 48 forks source link

Sajdakabir/mar 307 send meeting by date #544

Closed sajdakabir closed 2 weeks ago

sajdakabir commented 2 weeks ago

What did you ship?

Fixes:

Checklist:

OR:

coderabbitai[bot] commented 2 weeks ago

[!CAUTION]

Review failed

The pull request is closed.

📝 Walkthrough ## Walkthrough This pull request introduces several enhancements to the Google Calendar integration within the application. A new controller function, `getGoogleCalendarMeetingsByDateController`, is added to retrieve meetings for a specified date, utilizing a new service function, `getGoogleCalendarMeetingsByDate`. Additionally, modifications are made to the `redirectLinearOAuthLoginController` to change its response format from a redirect to a JSON object. New routes and minor updates in comments are also included, maintaining the overall structure of the existing code. ## Changes | File Path | Change Summary | |----------------------------------------------------------|-------------------------------------------------------------------------------------------------------| | `apps/backend/src/controllers/integration/calendar.controller.js` | - Added method: `getGoogleCalendarMeetingsByDateController`.
- Updated export statement to include the new controller. | | `apps/backend/src/controllers/integration/linear.controller.js` | - Modified `redirectLinearOAuthLoginController` to respond with a JSON object instead of redirecting. | | `apps/backend/src/routers/integration/calendar.route.js` | - Added route for `getGoogleCalendarMeetingsByDateController` at `/meetings/:date/`.
- Updated comment for clarity. | | `apps/backend/src/services/integration/calendar.service.js` | - Added method: `getGoogleCalendarMeetingsByDate(user, date)` to retrieve meetings for a specified date. | ## Possibly related PRs - **#530**: The changes in this PR involve modifications to the `calendar.controller.js` and `calendar.service.js` files, which are directly related to the Google Calendar integration, similar to the new `getGoogleCalendarMeetingsByDateController` function introduced in the main PR. Both PRs enhance the functionality of the calendar integration. ## Poem > 🐰 In the garden where calendars bloom, > Meetings now dance, dispelling the gloom. > With dates in our paws, we fetch with delight, > JSON responses, oh what a sight! > From Linear to Google, our paths intertwine, > Hopping through code, all functions align! 🌼

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://coderabbit.ai/docs) 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.
github-actions[bot] commented 2 weeks ago

Hey there! 👋

We require pull request titles to follow the Conventional Commits specification.

Valid types:

Format: type: description

Error details:

No release type found in pull request title "Sajdakabir/mar 307 send meeting by date". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat
 - fix
 - docs
 - style
 - refactor
 - perf
 - test
 - build
 - ci
 - chore
 - revert