Restore edits on start; Handle play mode

[jonathankap]

Summary by CodeRabbit

• New Features
  • Enhanced message handling for the reactor, allowing it to respond to both "EDITING" and "PLAY" commands for improved functionality.
  • Improved deactivation logic for the reactor, recognizing both "STOP_EDITING" and "STOP_PLAYING" messages.

[coderabbitai]

Walkthrough

Walkthrough

The changes enhance the message handling logic in the chrome extension's reactor. The listener now activates for both "EDITING" and "PLAY" messages, allowing for expanded modifications. Additionally, the reactor can be stopped by either "STOP_EDITING" or "STOP_PLAYING" messages. These updates broaden the operational capacity of the reactor in response to more states within the application.

Changes

Files	Change Summary
apps/mocksi-lite-next/src/pages/content/...	Expanded message handling logic to include "PLAY" for activation and "STOP_PLAYING" for deactivation, improving reactor responsiveness to multiple states.

Poem

In a world of edits and plays,
A rabbit hops through bright new ways.
With messages clear, the reactor’s in cheer,
As it dances and twirls, shedding all fears.
"Hop to it!" it sings, "Let the changes ring!" 🐇✨

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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 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 for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7946b8e and 00a8764.

Files selected for processing (1)

• apps/mocksi-lite-next/src/pages/content/mocksi-extension.tsx (2 hunks)

Additional comments not posted (2)

apps/mocksi-lite-next/src/pages/content/mocksi-extension.tsx (2)

87-87: LGTM! The changes are approved.

The logic for stopping the reactor with "STOP_EDITING" and "STOP_PLAYING" messages is correct and aligns with the PR objectives.

---

72-75: Verify request.data.edits is defined for "EDITING" and "PLAY" messages.

Ensure that request.data.edits is always defined when "EDITING" or "PLAY" messages are received to prevent potential runtime errors.

Run the following script to verify the presence of request.data.edits in the codebase:

[elg0nz]

👍

[fitzk]

nice haha