Skip to content

Update registry#1920

Merged
Siddharth2207 merged 3 commits intomainfrom
2025-06-12-update-registry
Jun 12, 2025
Merged

Update registry#1920
Siddharth2207 merged 3 commits intomainfrom
2025-06-12-update-registry

Conversation

@Siddharth2207
Copy link
Copy Markdown
Contributor

@Siddharth2207 Siddharth2207 commented Jun 12, 2025

Motivation

Update registry, resolves #1886

Checks

By submitting this for review, I'm confirming I've done the following:

  • made this PR as small as possible
  • unit-tested any new functionality
  • linked any relevant issues or PRs
  • included screenshots (if this involves a front-end change)

Summary by CodeRabbit

Summary by CodeRabbit

  • Chores
    • Updated an internal URL to reference the latest data source. No visible changes to the user experience.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 12, 2025

Walkthrough

The constant REGISTRY_URL in the codebase was updated to reference a new commit hash within its GitHub raw content URL. Additionally, the URL used in the fetch call for loading settings in the layout route was updated to the same new commit hash. No other files or exported entities were modified.

Changes

File(s) Change Summary
packages/webapp/src/lib/constants.ts Updated REGISTRY_URL to use a new commit hash in its URL string.
packages/webapp/src/routes/+layout.ts Updated fetch URL in load function and corresponding test to new commit hash.

Sequence Diagram(s)

No sequence diagram generated as the change is limited to URL updates.

Assessment against linked issues

Objective Addressed Explanation
Fix CORS error for arbitrum network (#1886) Changes only update URLs to new commit hashes; no CORS handling or network-specific fixes implemented.

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes detected.

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error https://github.com/npm/cli/issues
npm error A complete log of this run can be found in: /.npm/_logs/2025-06-12T10_19_12_196Z-debug-0.log

✨ Finishing Touches
  • 📝 Generate Docstrings

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

@Siddharth2207 Siddharth2207 self-assigned this Jun 12, 2025
@Siddharth2207 Siddharth2207 requested a review from hardyjosh June 12, 2025 08:52
@Siddharth2207 Siddharth2207 linked an issue Jun 12, 2025 that may be closed by this pull request
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5446a35 and 8693421.

📒 Files selected for processing (1)
  • packages/webapp/src/routes/+layout.ts (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build-tauri (ubuntu-22.04, true)
🔇 Additional comments (1)
packages/webapp/src/routes/+layout.ts (1)

154-156: Align test assertion with implementation
The unit test expectation has been updated to reference the new settings URL. This change matches the updated fetch logic and ensures the test remains valid.

Comment on lines 21 to 23
const response = await fetch(
'https://raw.githubusercontent.com/rainlanguage/rain.strategies/ff343647234ed635eb0b4b0c1862cf78665cc5ec/settings.json'
'https://raw.githubusercontent.com/rainlanguage/rain.strategies/0c7e62f4e1d773d2dde6c25720da2a7de446b011/settings.json'
);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Centralize settings URL usage
The fetch call now points to the updated commit, but hardcoding the raw URL here duplicates the constant defined in packages/webapp/src/lib/constants.ts. To prevent mismatches whenever the commit hash changes, import and reuse that constant instead of an inline string.

Example diff:

@@ import type { LayoutLoad } from './$types';
-import type { LayoutLoad } from './$types';
+import type { LayoutLoad } from './$types';
+import { SETTINGS_URL } from '$lib/constants';

@@
-		const response = await fetch(
-			'https://raw.githubusercontent.com/rainlanguage/rain.strategies/0c7e62f4e1d773d2dde6c25720da2a7de446b011/settings.json'
-		);
+		const response = await fetch(SETTINGS_URL);
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
const response = await fetch(
'https://raw.githubusercontent.com/rainlanguage/rain.strategies/ff343647234ed635eb0b4b0c1862cf78665cc5ec/settings.json'
'https://raw.githubusercontent.com/rainlanguage/rain.strategies/0c7e62f4e1d773d2dde6c25720da2a7de446b011/settings.json'
);
import type { LayoutLoad } from './$types';
import { SETTINGS_URL } from '$lib/constants';
export const load: LayoutLoad = async () => {
const response = await fetch(SETTINGS_URL);
// ...rest of your logic
};
🤖 Prompt for AI Agents
In packages/webapp/src/routes/+layout.ts around lines 21 to 23, the fetch call
uses a hardcoded URL string for the settings.json file, duplicating a constant
already defined in packages/webapp/src/lib/constants.ts. To fix this, import the
URL constant from the constants.ts file at the top of +layout.ts and replace the
inline string in the fetch call with this imported constant to ensure
consistency and easier maintenance.

@Siddharth2207 Siddharth2207 merged commit fdc289f into main Jun 12, 2025
16 checks passed
@coderabbitai coderabbitai Bot mentioned this pull request Nov 7, 2025
4 tasks
@coderabbitai coderabbitai Bot mentioned this pull request Feb 4, 2026
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CORS error for arbitrum network.

2 participants