🐛 Fix inspection functionality not working for Vue devtools

[devtobi]

Description

• Dynamically set optionsAPI mode in Vite config to support devtool inspector while developing

Reference
Closes #684

Summary by CodeRabbit

• Chores
  • Updated Vite configuration in frontend and web component projects to support dynamic environment-based configuration.
  • Introduced conditional Vue plugin options based on development mode.

The changes enhance build configuration flexibility and allow for environment-specific settings without altering core application functionality.

[coderabbitai]

Walkthrough

The pull request modifies the Vite configuration files for both refarch-frontend and refarch-webcomponent projects. The key change is transforming the static Vite configuration export to a dynamic function that accepts a mode parameter. This allows conditional configuration of the Vue plugin's optionsAPI feature, specifically enabling it during development mode while maintaining the existing server, resolve, and build configurations. Additionally, the vitest.config.ts files have been updated to utilize a similar dynamic export structure.

Changes

File	Change Summary
refarch-frontend/vite.config.ts	Updated Vite configuration to use dynamic export with mode-based configuration
refarch-webcomponent/vite.config.ts	Updated Vite configuration to use dynamic export with mode-based configuration
refarch-frontend/vitest.config.ts	Updated Vitest configuration to use dynamic export with configEnv parameter
refarch-webcomponent/vitest.config.ts	Updated Vitest configuration to use dynamic export with configEnv parameter

Assessment against linked issues

Objective	Addressed	Explanation
Enable Vue DevTools inspector [#684]	✅
Conditionally support OptionsAPI [#684]	✅

Poem

🐰 A config dance, dynamic and bright,
Where modes shift settings left and right,
DevTools now sparkle with glee,
Vue's magic flows, both wild and free!
Configuration rabbit hops with delight! 🎉

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 359e3dc and 624607f.

📒 Files selected for processing (2)

• refarch-frontend/vitest.config.ts (1 hunks)
• refarch-webcomponent/vitest.config.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build (refarch-backend)

🔇 Additional comments (2)

refarch-webcomponent/vitest.config.ts (1)

7-16: LGTM! Dynamic configuration supports Vue devtools inspection.

The transformation from static to dynamic configuration aligns with the PR objective. The change allows the Vite configuration to adapt based on the environment, which is necessary for enabling the Vue devtools inspection functionality.

refarch-frontend/vitest.config.ts (1)

7-21: LGTM! Configuration changes maintain consistency across projects.

The dynamic configuration implementation matches the pattern used in refarch-webcomponent while preserving the necessary Vuetify-specific settings. This ensures consistent behavior across both frontend projects.

Finishing Touches

• 📝 Generate Docstrings (Beta)

---

🪧 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>, 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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 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.

[simonhir]

LGTM