start using verbs and implement

[jordanpartridge]

Pull Request Template

Description

Please include a summary of the change and which issue is fixed. Also, include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

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 that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

• [ ] Test A
• [ ] Test B

Checklist:

Before you submit the pull request, please review the following checklist and mark all the completed items.

• [ ] I have performed a self-review of my own code.
• [ ] I have commented my code, particularly in hard-to-understand areas.
• [ ] I have made corresponding changes to the documentation.
• [ ] My changes generate no new warnings.
• [ ] I have added tests that prove my fix is effective or that my feature works.
• [ ] New and existing unit tests pass locally with my changes.
• [ ] Any dependent changes have been merged and published in downstream modules.

Screenshots (if applicable)

Include screenshots or gifs if your PR includes visual/UI changes.

Additional Notes

Add any other details about the PR here.

Summary by CodeRabbit

Release Notes

• New Features

  • Introduced new event classes: CommandFailed for error logging and RideSynced for notifying users upon ride synchronization.
  • Enhanced activity synchronization to filter and process only relevant 'Ride' activities.

• Bug Fixes

  • Improved error handling and reporting mechanisms during activity synchronization.

• Database Migrations

  • Added new tables: verb_events, verb_snapshots, and verb_state_events to support expanded functionality.

• Dependencies

  • Added new package hirethunk/verbs to enhance project capabilities.

[coderabbitai[bot]]

Walkthrough

## Walkthrough The pull request introduces significant enhancements to the `SyncActivities` command, focusing on improved error handling and event-driven architecture. New event classes, `CommandFailed` and `RideSynced`, are added to manage command failures and ride synchronization notifications, respectively. Additionally, several migration files are created to establish new database tables for verb events, snapshots, and state events, ensuring better data management. The `composer.json` file is also updated to include a new dependency, expanding the project's capabilities. ## Changes | File Path | Change Summary | |-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `app/Console/Commands/SyncActivities.php` | Enhanced error handling and event firing in the `handle` method; filtered activities by type 'Ride'; improved exception reporting in `fetchActivitiesPage` and `processActivity`; removed `logSyncResults`. | | `app/Events/CommandFailed.php` | Introduced `CommandFailed` class for handling command failure events with properties for command and message, including a logging method. | | `app/Events/RideSynced.php` | Added `RideSynced` class to handle ride synchronization events, sending notifications and logging activities related to rides. | | `composer.json` | Added new dependency: `hirethunk/verbs` with version constraint `^0.6.2`. | | `database/migrations/2024_04_16_115559_create_verb_events_table.php` | Created `verb_events` table with specified columns and migration methods. | | `database/migrations/2024_04_16_115559_create_verb_snapshots_table.php` | Created `verb_snapshots` table, including logic to migrate data from an old table if it exists. | | `database/migrations/2024_04_16_115559_create_verb_state_events_table.php` | Created `verb_state_events` table with necessary columns and migration methods. | ## Possibly related PRs - **#46**: Enhancements in the `SyncActivities.php` file regarding exception handling and logging align with the main PR's focus on improving error reporting mechanisms. - **#49**: Modifications to the `handle()` method in `SyncActivities.php` restructure logging related to syncing activities, relevant to the main PR's updates on logging. - **#64**: Introduces a notification for successful ride synchronization in `SyncActivities.php`, directly connecting to the main PR's updates regarding event firing after ride synchronization. - **#67**: Refinements in the `SyncActivities` command enhance error handling and modularize functionality, directly relating to the main PR's improvements in synchronization logic. ## Poem > 🐇 In the meadow, changes bloom, > Syncing rides, dispelling gloom. > Events now dance, both bright and bold, > With logs that sing of tales untold. > Command failures, we now embrace, > In this new world, we find our place! 🌼

---

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. ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.