fix(ui): Small fixes UI

[madeindjs]

Summary by CodeRabbit

• Bug Fixes

  • Improved layout and text overflow handling for the deploy button and header in the builder interface.
  • Enhanced stability in the sidebar component tree by adjusting root branch styling.
  • Improved PDF embedding by safely handling undefined page references.

• Tests

  • Added new test cases for dynamic user state handling with undefined values.
  • Introduced and updated mock functions in test suites for more comprehensive coverage.

• Refactor

  • Streamlined prop declarations in the embedded code editor for clearer default values and type enforcement.
  • Simplified validation logic in dynamic user state management for better reliability.

[coderabbitai]

Walkthrough

The changes span multiple files, focusing on refining type declarations, improving test coverage, updating mock functions, and enhancing UI layout and safety in value access. Prop definitions are made more explicit, new test cases are added, mock APIs are extended, CSS adjustments improve layout and overflow handling, and optional chaining is introduced for safer reactive reference access.

Changes

File(s)	Change Summary
src/ui/src/builder/BuilderEmbeddedCodeEditor.vue	Refactored prop definitions to explicit object-based syntax with types/defaults; improved initial value assignment using nullish coalescing.
src/ui/src/builder/BuilderHeader.vue	Added CSS class for deploy button; adjusted grid template columns for improved layout and overflow.
src/ui/src/builder/BuilderSwitcher.spec.ts src/ui/src/composables/useWriterTracking.spec.ts	Added mock function loadAndIdentifyChameleon to mocked WriterApi in tests.
src/ui/src/builder/sidebar/BuilderSidebarComponentTree.vue	Removed margin-top: -8px; from .rootBranch class in CSS.
src/ui/src/builder/useDynamicUserState.spec.ts	Added test for handling undefined valueType and value in user state, expecting empty string result.
src/ui/src/builder/useDynamicUserState.ts	Simplified validation logic; now only checks element type; handles undefined valueType/value as empty string.
src/ui/src/components/core/embed/CorePDF.vue	Added optional chaining for pages.value access in functions and watchers to prevent errors on null/undefined.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant BuilderEmbeddedCodeEditor
    User ->> BuilderEmbeddedCodeEditor: Mount component
    BuilderEmbeddedCodeEditor ->> BuilderEmbeddedCodeEditor: Set editor value (modelValue ?? "")

Loading

sequenceDiagram
    participant Test
    participant WriterApiMock
    Test ->> WriterApiMock: Call loadAndIdentifyChameleon()
    WriterApiMock -->> Test: Return mock result

Loading

Poem

In the garden of code, where the carrots grow neat,
We pruned our props and tidied our suite.
With mocks that now know a chameleon’s name,
And headers that flex in the layout game.
CSS trimmed, watchers safe and sound—
Another hop forward, with changes abound!
🥕

---

📜 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 4a4bd40 and 7d5c470.

📒 Files selected for processing (1)

• src/ui/src/components/core/embed/CorePDF.vue (3 hunks)

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

• src/ui/src/components/core/embed/CorePDF.vue

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

• GitHub Check: tests
• GitHub Check: tests (chromium)
• GitHub Check: tests (webkit)
• GitHub Check: tests (firefox)
• GitHub Check: build (3.11)
• GitHub Check: build (3.10)
• GitHub Check: build (3.9)
• GitHub Check: build (3.12)
• GitHub Check: build (3.13)
• GitHub Check: build (3.12)
• GitHub Check: build (3.10)
• GitHub Check: build (3.11)
• GitHub Check: build (3.13)
• GitHub Check: build (3.9)
• GitHub Check: Analyze (python)
• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Analyze (actions)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • 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 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.

[hackerone-code]

🔍 This pull request has been sent to HackerOne's PullRequest review team because our automation detected one or more changes with potential security impact or requires further evaluation. Experts are now being assigned to this review based on relevant expertise and will validate or dismiss any security findings accordingly and post their feedback as comments within this pull request.

⏱️ Latest scan covered changes up to commit 4a4bd40 (latest)

---

Check the status or cancel this secure code review here.