coderabbitai[bot]
commented
4 months ago Walkthrough
The updates primarily introduce support for Base Mainnet and Base Sepolia networks across various components, including environment configurations, migration scripts, and test cases. These changes ensure that the system can handle new network IDs, API keys, and URLs, and include the necessary logic for token management and project filtering based on these networks.
Changes
| Files | Change Summaries |
|---|---|
.github/workflows/develop-pipeline.yml, .github/workflows/master-pipeline.yml, .github/workflows/staging-pipeline.yml |
Added BASE_SCAN_API_KEY and BASE_SEPOLIA_SCAN_API_KEY to environment variables. |
config/example.env, config/test.env |
Added new environment variables for Base Scan API URLs and keys. |
migration/1716367359560-add_base_chain_tokens.ts |
Implemented migration to add base chain tokens to specific organizations. |
migration/data/seedTokens.ts |
Added new token entries in the seedTokens array. |
package.json |
Updated test scripts to include projectResolver.allProject.test.ts. |
src/entities/project.ts |
Added AcceptFundOnBase to the FilterField enum. |
src/provider.ts |
Added new network IDs and corresponding API configurations for Base Mainnet and Base Sepolia. |
src/resolvers/donationResolver.test.ts |
Updated valid transaction network IDs to include 8453 and 84532. |
src/resolvers/projectResolver.ts |
Added case for FilterField.AcceptFundOnBase to include Base Mainnet and Base Sepolia. |
src/resolvers/projectResolver.allProject.test.ts |
Added new test cases for filtering projects based on donation acceptance criteria on different networks. |
src/server/adminJs/tabs/donationTab.ts, src/server/adminJs/tabs/qfRoundTab.ts, src/server/adminJs/tabs/tokenTab.ts |
Added network options for Base Mainnet and Base Sepolia. |
src/services/chains/index.test.ts |
Added test cases for retrieving transaction details on Base Mainnet and Base Sepolia. |
src/utils/networksConfig.ts |
Added network configurations for Base Mainnet and Base Sepolia. |
src/utils/validators/graphqlQueryValidators.ts |
Updated managingFundsValidator to include Base Mainnet and Base Sepolia. |
src/utils/validators/projectValidator.ts |
Added support for Base Mainnet and Base Sepolia in isWalletAddressSmartContract. |
test/pre-test-scripts.ts |
Added token seeding logic for Base Mainnet and Base Sepolia. |
test/testUtils.ts |
Added entries for Base Mainnet and Base Sepolia in SEED_DATA. |
In fields of code, where logic flows, New networks rise where data goes. With keys and URLs, they stand, Base Mainnet, Sepolia, hand in hand. Tokens seeded, tests aligned, A future bright, with code refined.
[!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?
mohammadranjbarz
Summary by CodeRabbit
New Features
Tests
Chores
related to #1341