[3914] added flowMetaTheme in buildThemeConfigFromFlowMeta

[zesu22]

Purpose

Some theme values were unintentionally getting overwritten during runtime. This PR ensures that the actual theme configuration returned by the backend is properly mapped and prioritized across the UI components.

Enhance SDK theme building to support flowMetaTheme properties

Changes:

• Core Interfaces: Expanded the FlowMetaTheme interface in the JavaScript package to support border, shadows, spacing, and borderRadius properties.

• SDK Integration: Updated the buildThemeConfigFromFlowMeta method across both the React and Vue wrappers to properly inject and forward the flowMetaTheme configuration. This ensures all metadata-driven theme properties are correctly transported and applied down to the SDK.

Approach

Related Issues

• N/A

Related PRs

• N/A

Checklist

• Followed the contribution guidelines.
• Manual test round performed and verified.
• Documentation provided. (Add links if there are any)
• Tests provided. (Add links if there are any)
  • Unit Tests
  • Integration Tests
• Breaking changes. (Fill if applicable)
  • Breaking changes section filled.
  • breaking change label added.

Security checks

• Followed secure coding standards in WSO2 Secure Coding Guidelines
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.

[coderabbitai]

Warning

Review limit reached

@zesu22, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 56 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: c481d344-bf04-450f-a487-0128190514f5

📥 Commits

Reviewing files that changed from the base of the PR and between f3e97c5 and 09d3f04.

📒 Files selected for processing (3)

• packages/javascript/src/models/flow-meta.ts
• packages/react/src/utils/buildThemeConfigFromFlowMeta.ts
• packages/vue/src/utils/buildThemeConfigFromFlowMeta.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

_{Comment @coderabbitai help to get the list of available commands.}