fix: relayer success response

[songwongtp]

Description

Closes: #XXXX

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow-up issues.

I have...

• included the correct type prefix in the PR title, you can find examples of the prefixes below:
• confirmed ! in the type prefix if API or client breaking change
• targeted the correct branch
• provided a link to the relevant issue or specification
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• updated the relevant documentation or specification, including comments for documenting Go code
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

• Bug Fixes
  • Adjusted relayer setup flow to prevent duplicate success messages during configuration.
• Enhancements
  • Simplified and clarified success message instructions for setting up the Rapid relayer with cleaner command formatting and consolidated display in the terminal state.
  • Updated option label to "Generate a relayer config" and improved relayer config generation flow with analytics tracking.

[coderabbitai]

Walkthrough

Multiple calls pushing a relayer setup success message in various Update methods were removed, consolidating the message display to the TerminalState model’s View method. The success message content and formatting were revised for clarity and simplicity, with no other logic or control flow changes. Additionally, the WeaveInit model now supports the "Generate a relayer config" option, initializing a new relayer state and tracking analytics events accordingly.

Changes

Cohort / File(s)	Change Summary
Relayer Model UI State and Success Message models/relayer/init.go	Removed multiple pushes of the relayer success message from intermediate update states; appended the message only in the terminal view. Simplified and reformatted the success message content and styling.
WeaveInit Model Update for Relayer Option models/weaveinit/weaveinit.go	Added support for the "Generate a relayer config" option by initializing a new relayer state and model, tracking analytics events, and changing the option label from "Run a relayer". Minor type changes in analytics event property maps.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

A message once pushed here and there,
Now waits in terminal’s quiet air.
Commands laid out, simple and clear,
The relayer’s path draws near.
A rabbit hops with joy anew—
Clean code shines bright for me and you! 🐇✨

From weaveinit springs a fresh new way,
To generate configs without delay.
Options changed, events tracked true,
The relayer’s journey starts anew! 🚀🐰

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9a03f59 and 3ffa7ad.

📒 Files selected for processing (1)

• models/weaveinit/weaveinit.go (7 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• models/weaveinit/weaveinit.go

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Run Integration Tests on Ubuntu
• GitHub Check: Analyze (go)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/relayer-success-response

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this 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.

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: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3e135d9 and 9a03f59.

📒 Files selected for processing (1)

• models/weaveinit/weaveinit.go (6 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

models/weaveinit/weaveinit.go (8)

analytics/amplitude.go (3)

• AppendGlobalEventProperties (56-64)
• TrackEvent (73-91)
• NewEmptyEvent (67-71)

context/context.go (1)

• NewAppContext (38-52)

models/relayer/state.go (1)

• NewRelayerState (33-40)

context/path.go (1)

• SetMinitiaHome (38-40)

common/constants.go (1)

• MinitiaDirectory (17-17)

context/layout.go (1)

• SetWindowWidth (22-24)

analytics/constant.go (6)

• ComponentEventKey (19-19)
• RelayerComponent (15-15)
• FeatureEventKey (20-20)
• SetupRelayerFeature (87-87)
• InitActionSelected (37-37)
• OptionEventKey (22-22)

models/relayer/init.go (1)

• NewRollupSelect (61-105)

🔇 Additional comments (3)

models/weaveinit/weaveinit.go (3)

17-17: LGTM! Import addition is necessary and properly placed.

The relayer package import is required for the new RunRelayerOption functionality and is correctly positioned in alphabetical order.

---

107-107: LGTM! Good modernization to use any instead of interface{}.

The change from map[string]interface{} to map[string]any is a good modernization practice for Go 1.18+. All instances are consistently updated.

Also applies to: 124-124, 138-138, 156-156

---

151-166: LGTM! Well-structured implementation following established patterns.

The RunRelayerOption implementation correctly:

• Initializes the relayer state and context
• Sets up the Minitia home directory and window width
• Tracks analytics events with appropriate component and feature values
• Handles errors properly with panic model
• Returns the rollup selection model

The implementation is consistent with other option handlers in the same method.