Skip to content

Update doc gen for traces correctly#649

Merged
JasoonS merged 1 commit intomainfrom
docegen-traces
Jun 3, 2025
Merged

Update doc gen for traces correctly#649
JasoonS merged 1 commit intomainfrom
docegen-traces

Conversation

@JasoonS
Copy link
Contributor

@JasoonS JasoonS commented Jun 3, 2025

Pretty self explanitory I hope :)

Summary by CodeRabbit

  • Documentation

    • Updated documentation to reflect new "-traces" subdomain format for Eth Traces and Gnosis Traces network URLs.
    • Removed detailed guides for indexing Eth Traces and Gnosis Traces networks.
    • Clarified trace-specific endpoints in supported networks tables.
  • Chores

    • Minor formatting improvements and whitespace adjustments in configuration files.

@JasoonS JasoonS requested a review from Piroddi June 3, 2025 08:51
@vercel
Copy link

vercel bot commented Jun 3, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
envio-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 3, 2025 8:51am

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 3, 2025

Walkthrough

This update modifies documentation and scripts to standardize trace network endpoint URLs by appending "-traces" to the network ID in relevant URLs. It also removes two trace-specific documentation files, updates markdown generation scripts to reflect these changes, and excludes trace networks from certain generated docs. No code logic or exported entities are added or removed.

Changes

File(s) Change Summary
docs/HyperIndex/supported-networks/eth-traces.md,
docs/HyperIndex/supported-networks/gnosis-traces.md
Deleted documentation files for Eth Traces and Gnosis Traces indexing.
docs/HyperSync/HyperRPC/hyperrpc-url-endpoints.md,
docs/HyperSync/hypersync-supported-networks.md
Updated trace network URLs to use "-traces" subdomain format for Eth Traces and Gnosis Traces.
scripts/update-endpoints.js Refactored URL generation logic to append "-traces" for trace networks, excluded traces from some markdown outputs, and reformatted functions for clarity.
supported-networks.json Added a newline at the end of the file; no change to network entries.

Sequence Diagram(s)

sequenceDiagram
    participant Script as update-endpoints.js
    participant Docs as Markdown/Docs
    participant User

    User->>Script: Run endpoint update script
    Script->>Script: Check if network is a "traces" network
    alt If traces network
        Script->>Docs: Generate URLs with "-traces" suffix
        Script->>Docs: Exclude from HyperIndex markdown
    else Non-traces network
        Script->>Docs: Generate standard URLs
        Script->>Docs: Include in HyperIndex markdown
    end
    Script->>Docs: Write updated documentation
Loading

Poem

A hop and a skip, a dash and a dash,
Trace networks now sport a "-traces" sash!
Old docs are gone, the URLs are neat,
Scripts pruned and polished, endpoints replete.
With every update, we rabbits delight—
In tidy new docs and endpoints just right!
🐇✨

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

Copy link
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: 0

🧹 Nitpick comments (1)
scripts/update-endpoints.js (1)

272-275: LGTM! Function formatting improvement.

The reformatting of the sluggifyName function improves readability. Note: The console.log statement appears to be for debugging purposes.

Consider removing the console.log statement in the sluggifyName function if it's no longer needed for debugging:

const sluggifyName = (network) => {
-  console.log(network.name.toLowerCase().replace(/\s+/g, "-"))
  return network.name.toLowerCase().replace(/\s+/g, "-");
}
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 20f8ae4 and d835f67.

📒 Files selected for processing (6)
  • docs/HyperIndex/supported-networks/eth-traces.md (0 hunks)
  • docs/HyperIndex/supported-networks/gnosis-traces.md (0 hunks)
  • docs/HyperSync/HyperRPC/hyperrpc-url-endpoints.md (2 hunks)
  • docs/HyperSync/hypersync-supported-networks.md (2 hunks)
  • scripts/update-endpoints.js (8 hunks)
  • supported-networks.json (1 hunks)
💤 Files with no reviewable changes (2)
  • docs/HyperIndex/supported-networks/eth-traces.md
  • docs/HyperIndex/supported-networks/gnosis-traces.md
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/HyperSync/hypersync-supported-networks.md

53-53: Bare URL used
null

(MD034, no-bare-urls)


53-53: Bare URL used
null

(MD034, no-bare-urls)


62-62: Bare URL used
null

(MD034, no-bare-urls)


62-62: Bare URL used
null

(MD034, no-bare-urls)

docs/HyperSync/HyperRPC/hyperrpc-url-endpoints.md

45-45: Bare URL used
null

(MD034, no-bare-urls)


45-45: Bare URL used
null

(MD034, no-bare-urls)


54-54: Bare URL used
null

(MD034, no-bare-urls)


54-54: Bare URL used
null

(MD034, no-bare-urls)

🔇 Additional comments (7)
supported-networks.json (1)

5-5: LGTM! Good practice to add trailing newline.

This minor formatting improvement aligns with standard file formatting practices without affecting functionality.

docs/HyperSync/hypersync-supported-networks.md (1)

53-53: LGTM! Trace network URL standardization looks correct.

The URL changes properly append "-traces" to the chain ID portion for trace networks, creating clear differentiation between regular and trace endpoints:

  • Eth Traces: https://1-traces.hypersync.xyz
  • Gnosis Traces: https://100-traces.hypersync.xyz

This standardization improves clarity and consistency across the documentation.

Also applies to: 62-62

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

53-53: Bare URL used
null

(MD034, no-bare-urls)


53-53: Bare URL used
null

(MD034, no-bare-urls)

docs/HyperSync/HyperRPC/hyperrpc-url-endpoints.md (1)

45-45: LGTM! Consistent trace network URL updates across HyperRPC.

The URL changes maintain consistency with the HyperSync documentation, properly standardizing trace network endpoints:

  • Eth Traces: https://1-traces.rpc.hypersync.xyz
  • Gnosis Traces: https://100-traces.rpc.hypersync.xyz

This ensures uniform URL patterns across both HyperSync and HyperRPC documentation.

Also applies to: 54-54

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

45-45: Bare URL used
null

(MD034, no-bare-urls)


45-45: Bare URL used
null

(MD034, no-bare-urls)

scripts/update-endpoints.js (4)

71-80: LGTM! Function formatting improvement.

The reformatting of the emojiTier function improves readability without changing the logic.


94-98: LGTM! Trace network URL generation logic is correct.

The implementation properly detects trace networks and appends the "-traces" suffix to chain IDs in URLs:

const isTracesNetwork = chain.name.toLowerCase().includes("traces");
const chainIdSuffix = isTracesNetwork ? `-traces` : "";

This logic is consistently applied to both HyperSync and HyperRPC URL generation, ensuring uniform behavior across both services.

Also applies to: 118-121


202-205: LGTM! Markdown content generation includes trace network logic.

The trace network detection and URL modification logic is correctly integrated into the markdown content generation, ensuring that generated documentation files will have the proper trace network URLs with the "-traces" suffix.

Also applies to: 220-221


358-359: LGTM! Proper exclusion of trace networks from HyperIndex docs.

The filter to exclude trace networks from HyperIndex markdown generation aligns with the removal of dedicated trace documentation files:

!network.name.toLowerCase().includes("traces")  // Exclude traces networks from HyperIndex docs

This ensures that trace networks are handled through the standardized URL format rather than separate documentation files.

@JasoonS JasoonS merged commit 6757dd0 into main Jun 3, 2025
3 checks passed
@JasoonS JasoonS deleted the docegen-traces branch June 3, 2025 09:27
@DenhamPreen DenhamPreen mentioned this pull request Jul 29, 2025
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.

2 participants