Show connected RPC endpoint in `inspect` output

Open Beginner friendly
#164 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
typescript
Domain
cli

Research direction

Start in src/commands/inspect.ts, where the chain config and RPC URL are already available, then check src/commands/focused-inspect.ts for matching output. Update the inspect header to include the connected endpoint and verify that the output identifies both the chain and RPC URL.

Written by the indexing model from the issue text.

Description

enhancement

Problem

inspect shows "Pallets on polkadot" but doesn't show which RPC endpoint it connected to or where the metadata came from. When metadata resolution is wrong (see #161), there's no way to tell from the output alone.

Suggested Improvement

Include the RPC endpoint in the inspect header:

Pallets on preview-asset-hub (67)  [wss://previewnet.substrate.dev/asset-hub]

This is a trivial change — inspect.ts already has access to the chain config with the RPC URL. It provides diagnostic value especially when debugging metadata issues.

Key Files

  • src/commands/inspect.ts
  • src/commands/focused-inspect.ts
Dominant language
TypeScript
Stars
10
Forks
2
Avg merge
12h 35m
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from paritytech/polkadot-cli

All issues in paritytech/polkadot-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.