feat: add a wsh launch command

[oneirocosm]

This creates a new command wsh launch that will launch a widget that has been defined in the widgets.json file.

[coderabbitai]

Walkthrough

The pull request introduces a new command, launch, to the command-line interface. This command accepts a single argument representing the widget ID and includes the --magnify (or -m) flag to launch the widget in a magnified state. When executed, the command retrieves the full configuration with a specified timeout, checks for the widget's presence within both the user-defined and default widget lists, and constructs a block using the widget's block definition. The process involves creating the block by invoking the appropriate client command and logging the activity regarding the command execution. In addition, related documentation has been updated to describe the new command usage, including examples and details regarding the -m flag.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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

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

🧹 Nitpick comments (2)

cmd/wsh/cmd/wshcmd-launch.go (2)

36-40: Consider increasing the timeout for configuration retrieval.

A 2000ms timeout might be too short for large configurations, especially in high-latency environments or when dealing with extensive widget definitions.

-	config, err := wshclient.GetFullConfigCommand(RpcClient, &wshrpc.RpcOpts{Timeout: 2000})
+	config, err := wshclient.GetFullConfigCommand(RpcClient, &wshrpc.RpcOpts{Timeout: 5000})

---

51-64: Enhance the output message for better user feedback.

While the current output is functional, it could be more descriptive to help users understand the widget's state.

-	WriteStdout("launched widget %q: %s\n", widgetId, oref)
+	magnifiedStr := ""
+	if createBlockData.Magnified {
+		magnifiedStr = " (magnified)"
+	}
+	WriteStdout("launched widget %q%s: %s\n", widgetId, magnifiedStr, oref)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b4aeb80 and e43029b.

📒 Files selected for processing (2)

• cmd/wsh/cmd/wshcmd-launch.go (1 hunks)
• docs/docs/wsh-reference.mdx (1 hunks)

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

• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Analyze (go)
• GitHub Check: Build for TestDriver.ai

🔇 Additional comments (3)

cmd/wsh/cmd/wshcmd-launch.go (2)

14-27: LGTM! Command structure follows best practices.

The command definition and initialization follow standard cobra patterns with proper argument validation and flag registration.

---

42-49: LGTM! Widget lookup logic is robust.

The implementation correctly checks both user-defined and default widgets, with clear error messaging.

docs/docs/wsh-reference.mdx (1)

671-700: LGTM! Documentation is comprehensive and accurate.

The documentation clearly explains the command's functionality, flags, and usage patterns, with helpful examples and tips.