coderabbitai[bot]
commented
3 months ago Walkthrough
The recent updates to the Hestia application introduce a new configuration parameter, IS_BRIDGE_ENABLED, which controls the availability of the bridge feature. This parameter affects various components, middleware, and hooks to toggle the bridge functionality based on environment settings. Additionally, metadata has been added to the layout, and improvements have been made to the handling of cross-chain transfers and asset selection logic.
Changes
| Files | Change Summary |
|---|---|
apps/hestia/next.config.js |
Added IS_BRIDGE_ENABLED declaration to the nextConfig object. |
apps/hestia/src/app/layout.tsx |
Added Metadata import and metadata constant with title, description, and keywords. |
apps/hestia/src/components/thea/connectAccount.tsx |
Removed onClose() call within the ContentComponent function. |
apps/hestia/src/components/ui/Header/index.tsx, .../responsiveMenuModal.tsx |
Introduced isBridgeDisabled variable to conditionally disable bridge feature in the UI. |
apps/hestia/src/hooks/useBridge.ts |
Added imports, modified functions, handled errors, and added callbacks for cross-chain transfers. |
apps/hestia/src/middleware.ts |
Added check for isBridgeEnabled to redirect requests if the bridge feature is disabled. |
packages/core/src/config/index.ts, .../types.ts |
Introduced isBridgeEnabled parameter to the configuration based on IS_BRIDGE_ENABLED environment variable. |
packages/core/src/constants/notifications.ts |
Added new crossChainTransfer notification type for successful cross-chain transfers. |
packages/core/src/hooks/useTheaConfig.tsx |
Updated useTheaConfig hook to include connector in dependency array and adjusted query logic. |
packages/core/src/providers/user/thea/index.tsx |
Refactored asset selection logic and removed onRefetchTransferConfig function. |
In Hestia's code, a bridge now stands, Enabled by the env's commands. Metadata shines with title bright, Guiding users through the night. Cross-chain transfers, smooth and swift, A rabbit's touch, a coder's gift. 🐇✨
[!TIP]
New Features and Improvements
## Review Settings Introduced new personality profiles for code reviews. Users can now select between "Chill" and "Assertive" review tones to tailor feedback styles according to their preferences. The "Assertive" profile posts more comments and nitpicks the code more aggressively, while the "Chill" profile is more relaxed and posts fewer comments. ## AST-based Instructions CodeRabbit offers customizing reviews based on the Abstract Syntax Tree (AST) pattern matching. Read more about AST-based instructions in the [documentation](https://docs.coderabbit.ai/guides/review-instructions#ast-based). ## Community-driven AST-based Rules We are kicking off a community-driven initiative to create and share AST-based rules. Users can now contribute their AST-based rules to detect security vulnerabilities, code smells, and anti-patterns. Please see the [ast-grep-essentials](https://github.com/coderabbitai/ast-grep-essentials) repository for more information. ## New Static Analysis Tools We are continually expanding our support for static analysis tools. We have added support for `biome`, `hadolint`, and `ast-grep`. Update the settings in your `.coderabbit.yaml` file or head over to the settings page to enable or disable the tools you want to use. ## Tone Settings Users can now customize CodeRabbit to review code in the style of their favorite characters or personalities. Here are some of our favorite examples: - Mr. T: "You must talk like Mr. T in all your code reviews. I pity the fool who doesn't!" - Pirate: "Arr, matey! Ye must talk like a pirate in all yer code reviews. Yarrr!" - Snarky: "You must be snarky in all your code reviews. Snark, snark, snark!" ## Revamped Settings Page We have redesigned the settings page for a more intuitive layout, enabling users to find and adjust settings quickly. This change was long overdue; it not only improves the user experience but also allows our development team to add more settings in the future with ease. Going forward, the changes to `.coderabbit.yaml` will be reflected in the settings page, and vice versa. ## Miscellaneous - Turn off free summarization: You can switch off free summarization of PRs opened by users not on a paid plan using the `enable_free_tier` setting. - Knowledge-base scope: You can now set the scope of the knowledge base to either the repository (`local`) or the organization (`global`) level using the `knowledge_base` setting. In addition, you can specify Jira project keys and Linear team keys to limit the knowledge base scope for those integrations. - High-level summary placement: You can now customize the location of the high-level summary in the PR description using the `high_level_summary_placeholder` setting (default `@coderabbitai summary`). - Revamped request changes workflow: You can now configure CodeRabbit to auto-approve or request changes on PRs based on the review feedback using the `request_changes_workflow` setting.
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?
netlify[bot]
Description
For Bridge page, we need to create a flag which can be controllered by AWS in environment variables so that it can enable/disable Bridge page accordingly.
Fix THEA withdrawal issue on switching chain
Notification for Cross chain transfer
Title and Description added for Orderbook
Checklist