Enable Devtools Flag for Debugging in Production Environment

[devleejb]

What this PR does / why we need it:
This PR activates the enableDevtools flag in the production environment, allowing for easier debugging using Devtools.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:
Enabling the Devtools in the production environment can provide developers with crucial insights and tools for debugging potential issues efficiently.

Does this PR introduce a user-facing change?:

NONE

Additional documentation:

Checklist:

• Added relevant tests or not required
• Didn't break anything

Summary by CodeRabbit

• New Features
  • Enhanced document handling with development tools enabled for better debugging.
• Chores
  • Updated environment configuration for production by removing the development mode declaration.

[coderabbitai]

Warning

Review failed

The pull request is closed.

Walkthrough

The recent changes focus on streamlining the production environment and enhancing the debugging capabilities in the development process. The NODE_ENV=development declaration has been removed from frontend/.env.production to avoid any conflicts in the production environment. Additionally, the useYorkieDocument hook now includes an enableDevtools parameter to facilitate development tool integration.

Changes

Files	Change Summary
frontend/.env.production	Removed the NODE_ENV=development declaration.
frontend/src/hooks/useYorkieDocument.ts	Added enableDevtools parameter to useYorkieDocument function to enhance debugging.

Poem

In code's vast garden, where secrets lie,
A tweak was made beneath the sky.
Production clean, no dev's disguise,
And tools for Yorkie, sharp and wise.
Debug in ease, the changes fly,
With clarity, the systems rise.
🌿✨🐇

---

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
• Mastodon
• Reddit
• LinkedIn

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 Configration 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.