ui: preview

[reez]

Description

Notes to the reviewers

Changelog notice

Checklists

All Submissions:

• I've signed all my commits
• I have formatted my code with swift-format per .swift-format file

New Features:

• I've added tests for the new feature
• I've added docs for the new feature

Bugfixes:

• This pull request breaks the existing API
• I've added tests to reproduce the issue which are now passing
• I'm linking the issue being fixed by this PR

Summary by CodeRabbit

• New Features

  • Added conditional previews for various views (e.g., BitcoinView, OnboardingView, PaymentsView) that are only visible in debug mode, enhancing the development experience.

• Bug Fixes

  • No bug fixes were introduced in this release.

• Documentation

  • No changes to documentation were made.

• Chores

  • Improved the control flow for preview rendering in multiple views, ensuring they are excluded from release builds to optimize performance.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes involve the introduction of conditional compilation blocks using #if DEBUG directives across multiple Swift files. These directives encapsulate preview sections for various views, ensuring that the previews are only included in debug builds and not in release versions. This modification maintains the existing functionality of the views while controlling the visibility of the previews based on the build configuration.

Changes

Files	Change Summary
LDKNodeMonday/View/Home/BitcoinView.swift, OnboardingView.swift, PaymentsListView.swift, PaymentsView.swift, BIP21View.swift, JITInvoiceView.swift, ReceiveView.swift, AmountView.swift, StartView.swift, ChannelAddView.swift, ChannelDetailView.swift, ChannelsListView.swift, SeedView.swift, NodeIDView.swift, DisconnectView.swift, PeerView.swift, PeersListView.swift	Added #if DEBUG directives to encapsulate preview sections, ensuring they are included only in debug builds.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant DebugBuild
    participant ReleaseBuild

    Developer->>DebugBuild: Compile code with previews
    DebugBuild->>Developer: Show previews for views

    Developer->>ReleaseBuild: Compile code without previews
    ReleaseBuild->>Developer: Exclude previews from build

Loading

Poem

🐇
In the code, a tweak so bright,
Previews dance in debug light.
When the build is set to play,
Mock views hop and sway all day!
In release, they hide away,
A joyful change, hip-hip-hooray!
🌼

Tip

We have updated our review workflow to use the Anthropic's Claude family of models. Please share any feedback in the discussion post on our Discord.

---

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